feat(driver): BundleDriver for driving bundles to completion

[Evalir]

Adds a simple BundleDriver trait, which can drive bundles to completion.

Conceptually, it starts from an EvmNeedsTx state, and ends there. This means that this driver simply allows to run a group of transactions, while applying post-multi-tx logic after. It does not open or close blocks. This also allows us to run several bundles, one after another.

This BundleDriver trait is then composed with a BlockProcessor struct, which then takes charge of implementing a BundleDriver for a combination of a bundle type, and a response type. This allows us, for example, to quickly grab bundles that conform to flashbots bundles, simulate them, and return a properly calculated & formatted response. Vanilla impls for EthCallBundle & EthSendBundle are also provided which do not accumulate results.

A few macros were also added, mirroring eyre macros:

• unwrap_or_trevm_err!: Unwraps a Result, returning the value if successful, or returning an errored Trevm if not.
• trevm_ensure!: Executes a condition, returning an errored Trevm if not successful.
• trevm_bail!: Returns an errored Trevm with the provided error.

And lastly, try_with_* fns were added to have fallible with_* functions. The behavior of these was modified as well to use clone instead of mem::take to avoid having default values, which might be unexpected for the user.

• Driver trait
• sample alloy-rpc-types-mev implementation

fixes ENG-311

[prestwich]

the way this is implemented will cause anything not set by the filler to be default value. do we want that to be the case? or should we not use std::mem::take in with_block/try_with_block ?

[prestwich]

I think we should remove the mem::takes and instead clone the env

[prestwich]

looking good. Almost done

also needs try_with_cfg and try_with_tx (unless I'm blind)