…reum_rust into levm/refactor/db

…reum_rust into levm/refactor/db

…reum_rust into levm/refactor/db

…reum_rust into levm/refactor/db

…to levm-ethereum-rust-integration

**Motivation**

<!-- Why does this pull request exist? What are its goals? -->
fix some things generic_call in l1 integration because of merge.

**Description**

<!-- A clear and concise general description of the changes this PR
introduces -->

<!-- Link to issues: Resolves #111, Resolves #222 -->

Closes #issue_number

**Motivation**

<!-- Why does this pull request exist? What are its goals? -->

Eventually, we want to stop using revm and replace it with levm. The
integration is a work in progress in this PR
#1029.

This PR aims to be the first step. It aims to prepare the current
codebase so that both implementations can coexist while levm continues
to be developed and does not disturb the rest of the development. When
the time to remove revm comes, it'd be easier with this proposal since
it'd require removing the code under the #[cfg(not(feature = "levm"))]
and after that, to remove the feature flag definitively.

**Description**

<!-- A clear and concise general description of the changes this PR
introduces -->

- Adds the `levm` feature flag to the `vm` and `blockchain` packages,
and to the `ethereum_rust` binary.
- In `vm`, add `execute_block` implementation that uses `levm` and use
it when `levm` feature flag is set. Use the original implementation if
not.
- In `blockchain`, add `add_block` implementation that uses `levm` and
use it when `levm` feature flag is set. Use the original implementation
if not.

---------

Co-authored-by: Jeremías Salomón <[email protected]>
Co-authored-by: JereSalo <[email protected]>

…to levm-ethereum-rust-integration

Co-authored-by: Ivan Litteri <[email protected]>