Need to implement JournalDB and beam sync in AccountStateDB

[jangko]

Both GeneralStateTest and BlockChainTest now turned off state trie pruning when running tests.
With the introduction of EIP2200, some tests will fail if we turn on state trie pruning.

We cannot longer evade the need to implement a JournalDB.
I did not implement the JournalDB during EIP2200 implementation because we need not only a JournalDB, but also an AccountStateDB that can have beam sync turned on.
in the end the new AccountStateDB should have this features:

• taking state snapshot
• revert/rollback to old state by some ID/version
• discard snapshot
• able to jump back to historical state by ID/version and then jump forward during transaction execution with or without state trie pruning.
• turn state trie pruning on/off
• storage trie also have their own virtual container without depend on state trie pruning turned off
• turn beam sync on/off

[jangko]

we have a working AccountsCache that works similar to the JournalDB. beam sync is not relevant anymore. closing