feat: implemented manual deserialization of AccountInfo struct

[Pratham1812]

Implemented Manual Deserialization for AccountInfo to Support eth_getAccountInfo RPC

Fixes #2564

Problem

Currently, fetching account information requires multiple RPC calls:

let (nonce, balance, code) = tokio::join!(nonce, balance, code);

This is inefficient when eth_getAccountInfo can provide all data in a single call.

Solution

Implemented manual Deserialize for AccountInfo that:

• Supports both REVM internal format and RPC response format
• Auto-computes code_hash when only code is provided (RPC scenario)
• Maintains backward compatibility with existing serialized data
• Supports both code_hash and codeHash field names

Field Name Compatibility

The deserializer accepts both naming conventions:

• code_hash - Rust/REVM internal format (snake_case)
• codeHash - JSON-RPC standard format

Supported Formats

Current REVM format (backward compatible):

{"balance": "0x1000", "nonce": 42, "code_hash": "0xabc...", "code": "0x608..."}

RPC format (new optimization):

{"balance": "0x1000", "nonce": 42, "code": "0x608..."}

code_hash computed automatically

CamelCase RPC format:

{"balance": "0x1000", "nonce": 42, "codeHash": "0xabc..."}

[codspeed-hq]

CodSpeed Performance Report

Merging #2830 will not alter performance

_{Comparing Pratham1812:alpha/rpc (52f8dc4) with main (dfe1fdb)}

Summary

✅ 171 untouched benchmarks

[Pratham1812]

@mattsse @rakita If you guys could please review this.