feat: State with account status

[rakita]

Model account states to cover all possible state that transaction can change it

Model can be found here
Old model
New model

And create cached/transition/bundle states that can easily create reverts on those states.

States interconnection can be seen here:

EVM State
(It has both original/present storage and new account and storage acts as a access list.)
|
|
V
[Cache State] Fetches data from database and get updated from EVM state. Allows us fewer layer to fetch data from database.
|        \
|         \
|          [Transitions State] contains changes related to transition (Mostly block). It has original account/storage/status (Needed for Loaded account). It is used for creating Reverts. 
|          |
|          V
|          [Bundle state] (It has Reverts and plain state, Original storage is not needed) One of reasons why this is the case, is because when reverting of canonical chain we can't get previous storage value. And it is not needed.
|       /
|    /
v
database

this is still WIP!

[rakita]

tests were checked locally.

[rakita]

This PR synced on 17M blocks so we can assume initial sync works as expected.

There are few more bugs found related to reverts (changesets in reth) that still need to be addressed

• #591
• #590

We are merging this code and will iterate on it so we can unblock other teams that depend on revm.