Execution over state snapshots

One of the main features of Erigon3 is moving most of the state content (i.e. account/storage/code) and its validity proof (i.e. commitment) to snapshot flat files. This architectural change requires deep modifications also to the data model in the database (e.g. state history indexing) and to the execution staged pipeline.

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

*Transaction-level execution*
- [ ] #2312
- [ ] porting execution integration tests from E2 to E3
- [ ] new state data model in MDBX (i.e. different state tables)
- [ ] transaction-level state history granularity

*Block-level execution*
- [ ] new MPT algorithm implementation
- [ ] collapse execution and post-execution stages in staged pipeline
- [ ] in-process Temporal API endpoints (local)
- [ ] out-of-process Temporal API endpoints (remote)