feat: panic on invalid account lookups

[ed255]

After this was merged privacy-ethereum/zkevm-specs#354 the rule for opcodes that can access non-existing accounts is to first read the CodeHash, and only if it's not 0 (meaning that the account exists), proceed with other account field reads. If a field read is performed to a non-existing account, this may end up mapping to an MPT account field proof for a non-existing account (which are not supported); so the MPT proof would be impossible to generate. We can add some checks to make sure we don't implement any circuit that generates this situation; but we can even add more sanity checks to detect possible bugs early. In particular we can check for each account field lookup (either read or write):

• That a READ doesn't change the field value
• That the previous value matches the account field value in the StateDB
• That no read is done to a field other than CodeHash to a non-existing
  account (only CodeHash reads with value=0 can be done to non-existing
  accounts, which the State Circuit translates to MPT
  AccountNonExisting proofs lookups).

If any of these two points don't hold, the corresponding chain of MPT proofs
can't be generated.

In order to perform this checks in a single place, I've moved the logic to update the accounts in the StateDB performed by the circuit input builder in a single place, after the check (instead of requiring each bus-mapping opcode implementation to do it by themselves).

With these checks I found some bugs in the callop and error_oog_call, which I have fixed.

As a bonus I added the method debug_print_txs_steps_rw_ops to the witness::Block which prints all the rw operations (with their content) of each step in each tx, which was very useful for debugging.

Resolve #1084

Depends on #1069

[ChihChengLiang]

LGTM. I added some feedback.