feat: bus mapping for sload and sstore

[lispc]

Some explanation:

1. implement bus mapping for sload and sstore, and rewrite tests
2. in sstore gas calculation, EVM needs "CommittedState", which is the storage state value before current transaction. So dirty_storage is added to statedb.rs, just like StateDB in go-ethereum.
3. Some minor improvements for debugging experience: (1) enable env logger in tests (2) log::debug relationship mappings between global lookup index and lookup index of each rw type, so from circuit lookup error msg we can find which lookup is wrong more easily.
4. Change docker of integration-tests from stable to nightly, since currently only nightly geth has refund in trace.

Some review comments from old PR #418

1. As for refund and geth docker image upgrade, comments added in docker compose file in integration tests
2. For those Rust struct which implements Copy trait, cargo clippy will suggest use *reference rather than reference.clone()

A questions:

in zkevm circuits, if the tests are already written in bus mapping, will it be reasonable to write very similar tests in bus mapping again?

[CPerezz]

Hey @ChihChengLiang I can take this as I already reviewed the previous PR related to this. So I have the background already.

As you prefer, but happy to do it! :)

[CPerezz]

Overall looks good!! Thanks for working on this!

Left some comments and questions! :)

[CPerezz]

LGTM!

Thanks for this work @lispc 👍

[CPerezz]

in zkevm circuits, if the tests are already written in bus mapping, will it be reasonable to write very similar tests in bus mapping again?

Not sure I follow. But I think that it's safe to have tests in both sides even if they have some overlap TBH. As they might help to catch different kinds of errors as well as different missing API methods or similar stuff.