feat(api): add EIP-7966 eth_sendRawTransactionSync method

[coffeexcoin]

What ❔

Implement eth_sendRawTransactionSync API method to add EIP-7966 support to zksync era API.

sendRawTransactionSync uses the existing new block pubsub broadcast under the hood to check for transaction inclusion, on new blocks, while racing a user specified timeout (with default and node-configurable max) for inclusion.

Why ❔

With the v29 release and fast (200ms) blocks, dapps can benefit greatly by using synchronous calls for transaction submission to receipt, instead of having to poll for the receipt.

EIP-7966 has clear benefits for a number of onchain use cases:

• Trading. DEXs, CLOBs, and other trading apps can double their fee revenue by processing twice as many transactions per second, with no modification to block times or gas limits. The increased speed also allows these apps to offer tighter spreads, reduce stale quotes, and increase order execution probability – all of these improve UX.
• Gaming. Many onchain games translate rapid, repeated in-game actions (e.g. moves, item trades, crafting, etc.) into individual transactions, each of which generates a polling loop under today’s eth_sendRawTransaction paradigm. EIP-7966’s introduction of synchronous receipts reduces the load on RPCs by eliminating those loops and provides smoother gameplay for users.
• Payments. Onchain payments apps with high volumes can process more payments – and therefore generate more fees – with EIP-7966’s eth_sendRawTransactionSync method. This method also allows them to confirm payments faster and eliminate the anxiety users get waiting for a big transfer to be confirmed – a huge UX win.

Is this a breaking change?

• Yes
• No

Operational changes

Two new configuration values:

• send_raw_tx_sync_default_timeout_ms: default 2000 (2 seconds) per recommendation in EIP
• send_raw_tx_sync_max_timeout_ms: default 10000 (10 seconds) - prevents callers from very-long/infinite duration calls by specifying an unreasonable transaction inclusion timeout

Checklist

• PR title corresponds to the body of PR (we generate changelog entries from PRs).
• Tests for the changes have been added / updated.
• Documentation comments have been added / updated.
• Code has been formatted via zkstack dev fmt and zkstack dev lint.

[Deniallugo]

@coffeexcoin LGTM, but please make sure that lints are passing