db: move LocalState/RemoteState to execution, StateReader to kv

[battlmonstr]

db/state module is being repurposed for the low level e3 state implementation. It contains the eth state implementation that is not generic enough to be in db/datastore (akin SharedDomains vs Aggregator split in erigon). "low level" means that db/state must not depend on db/kv API.

In relation to this 2 refactorings are made:

1. move StateReader from db/state to db/kv. Rationale: StateReader is a client on top of the kv API exposing a particular facet the kv API (similar to what db/kv/StateChangesStream is doing as well).
2. move LocalState/RemoteState to execution. Rationale: LocalState/RemoteState are also clients on top of the kv API (or a lower level direct API) that adapt it to the core State interface abstraction used in relation to the EVM execution. The db::kv::api::Transaction::create_state method is replaced with execution::StateFactory. Now kv::api::Transaction is more decoupled from the EVM execution needs, and more closely represents the temporal KV API.

As a result, db/state does not depend on db/kv anymore. On the contrary, it is now possible to put code in db/kv that depends on db/state as needed.