core/state, light, trie: add UpdateContractCode to the Trie interface

[gballet]

Rationale: verkle trees store the code inside the trie. This PR changes the interface to pass the code, as well as the dirty flag to tell the trie package if the code is dirty and needs to be updated. This is a no-op for the MPT and the odr trie.

[gballet]

feedback by Martin during standup:

• What happens when the code is overwritten/deleted? For deletion, codesize values should be written to disk to erase things, for the overwrite, things are more complicated and need to be tested.
• as @rjl493456442 also pointed out, merging the code update with the tree update is uncanny, because the code DB update is only done to the dirty state. Even though there will be a check for dirty in the verkle implementation, it's better to streamline the client code by adding a new state update function that takes the tree as a parameter instead of the other way around.

[rjl493456442]

I think we can add a function UpdateContractCode(address common.Address, codeHash common.Hash, code []byte) to the Trie interface.

It's a bit weird that contract code is associated with a Trie, but we can leave it until we introduce StateReader/StateWriter interface.

---

The main difference between Verkle and MPT is: verkle puts everything in a single trie with its own (1) resource identifier scheme, defined https://notes.ethereum.org/@vbuterin/verkle_tree_eip (2) state encoding scheme.

But MPT has two-layer tree structure, and also stores contract code directly in key-value store by using hash as the identifier.

The better abstraction is: treat each state scheme as a state provider for EVM to consume/write-back. We can hide all the details inside of the implementation instead of exposing them in statedb package.

---

The current abstraction is not suitable between MPT and Verkle(and LES). The proper abstraction is:

• define StateReader/StateWriter in state package for accessing/writing back states
• define StateHasher in state package for deriving the hash root of state

The StateReader needs to provide APIs like:

• GetAccount(address common.Address) *types.StateAccount
• GetStorage(address common.Address, key []byte) []byte
• GetContractCode(address common.Address, codeHash common.Hash, /* offset uint64*/) []byte

The StateWriter needs to provide APIs like:

• UpdateAccount(address common.Address, account *types.StateAccount)
• UpdateStorage(addr common.Address, key, value []byte)
• UpdateContractCode(address common.Address, codeHash common.Hash, code []byte)
• DeleteAccount(address common.Address)
• DeleteStorage(addr common.Address, key []byte)
• DeleteContractCode(address common.Address, codeHash common.Hash)
• Commit() (common.Hash, *trienode.NodeSet)

The StateHasher needs to provide API like:

• Hash() common.Hash

Btw it will be a big change. So I purpose to add UpdateContractCode(address common.Address, codeHash common.Hash) as the first step.

[holiman]

Sure, it shouldn't break anything, so if you want it for easier verkle-integration, I guess that's fine