Use IPC instead of HTTP for performance

[RogerPodacter]

Note

Switches RPC to a new EthRpcClient with IPC/JWT engine support, adds memoized GethDriver.get_l1_attributes, updates call sites, and removes GethClient.

• Backend / RPC Layer:
  • EthRpcClient enhancements: Adds IPC transport with UNIX sockets, JWT auth support, incremental request IDs, configurable retries, and response parsing helpers; introduces EthRpcClient.l2_engine for authenticated engine calls.
  • GethDriver updates: Switch client to EthRpcClient.l2_engine, non_auth_client to EthRpcClient.l2; add memoized get_l1_attributes(l2_block_number) (moved from old client).
  • Callsite changes: Replace GethDriver.client.get_l1_attributes(...) with GethDriver.get_l1_attributes(...) in app/jobs/gap_detection_job.rb and app/services/eth_block_importer.rb.
  • Removal: Delete deprecated lib/geth_client.rb.

^{Written by Cursor Bugbot for commit 29dc822. This will update automatically on new commits. Configure here.}

[cursor]

Bug: IPC Detection Fails on HTTP URLs

The detect_mode method might incorrectly classify HTTP URLs as IPC. This happens because its IPC detection logic, specifically checking for '.ipc' in the URL string and using File.socket? on potentially unstripped HTTP URLs, can lead to misidentification. This can cause the client to attempt IPC connections to HTTP endpoints, resulting in connection failures.