rpcdaemon: state access using temporal KV

[canepat]

One of the main features of Erigon3 is moving most of the state content and its validity proofs (i.e. account/storage/code/commitment) to snapshot flat files. This change is also associated with an extension of the KV internal gRPC interface, named temporal KV.
It becomes natural using such temporal KV as a basis for porting our RPCDaemon module into the Erigon3 realm: first of all, implementing the out-of-process access, then switching to the embedded in-process version (this will require full support for Erigon3 snapshots).

This is the main tracking issue. Individual issues are listed below:

• KV: temporal direct and gRPC client + server skeleton #2024
• node: unit tests for temporal KV gRPC client #2026
• rpcdaemon: tx ID in client-side local/remote transaction #2068
• state access refactoring rpcdaemon: refactor chain and state access layer #2084 rpcdaemon: extract receipts out from chain #2100 rpcdaemon: move read_chain_config to chain storage #2104 rpcdaemon: refactoring to use db::storage_prefix utility #2116 rpcdaemon: refactoring state access #2129
• transaction/cursor hierarchy refactoring rpcdaemon: extract BackEnd out from Transaction hierarchy #2098 rpcdaemon: refactoring to separate SplitCursor from Cursor #2125 rpcdaemon: move transaction/cursor hierarchy to db #2136 db: KV begin_transaction as txn factory #2175
• state changes stream on generic KV API db: state change stream and cache on generic KV API #2168
• paginated temporal KV API (domain/history/index) db: paginated sequence for temporal KV API #2186 db: temporal KV client index_range API via gRPC #2189 db: temporal KV client history_range API via gRPC #2198 db: temporal KV client domain_range API via gRPC #2202 db: temporal KV client history_seek API via gRPC #2207 db: temporal KV client domain_get API via gRPC #2210
• implement state access V3 (StateReader, AsyncRemoteState) with temporal KV API (domain/history/index) core: decode account from E3 encoded storage #2251 db: support for E3 data format in remote state reader #2253