feat: introducing EvmWiring, a chain-specific configuration

[Wodann]

Experiment to see whether it would be possible to separate optimism and mainnet SpecIds and other types, such as HaltReason.

I'm curious to hear whether any of this is in line with #918

Supercedes #1378 (to allow editing by maintainers)

[Wodann]

Why would you want to restrict Block to all those generics:

#[auto_impl(Arc)]
pub trait Block<ChainSpecT: EvmSpec>: Debug {

It Looks brittle. I would try with associated types (for Tx) on Block, maybe this is a good path.

Sure, in this case we that might simplify things.

However, there are some places where we need all or large parts of the RuntimeSpec, which is a constrained version (additional trait bounds) of ChainSpec (not the Database and ExternalContext).

For the exact reason you mention, we don't want to pollute our codebase with the ExternalContext and Database associated types, especially since those are not types with a 'static lifetime - in our use case.