Add support for L1 to L2 message log syncing

[t00ts]

Introduces functionality to sync L1 to L2 message logs, improving our ability to track cross-chain interactions.

Key Changes

1. Added get_logs method to the Ethereum client:
   • Allows fetching logs for a specified block range
   • Implements recursive fetching with automatic range splitting for large queries
2. Implemented bulk syncing of L1ToL2MessageLog:
   • Fetches logs from the last synced L1 block up to the current state
   • Stores these logs for later matching with L2 transactions
3. Enhanced L1 sync process:
   • Bulk fetches logs at the beginning of execution
   • Waits for L2 blocks and matches l1_handler transactions with corresponding L1 transaction hashes
4. Introduced L1BlockNumber and L1TransactionHash types to avoid confusion

Closes #2243

[kkovaacs]

I've added a quite a few comments, most of them in these categories:

• using structured fields in tracing macros: https://docs.rs/tracing/latest/tracing/index.html#recording-fields
• we should be adding a newtype for L1 block number because we seem to be mixing L1/L2 block numbers at a few places
• using storage row accessors and type conversions for L1 block number / L1 block hash instead of ad-hoc conversions in storage code

[kkovaacs]

Another thought: the specification seems to require us returning the L2 transaction statuses for an L1 transaction hash in sending order. We do not currently store any information related to that -- we probably should?

[t00ts]

Closed in favor of #2301