refactor(evm): use EvmEnv::with_limits() for evm limit configuration

[rezzmah]

Motivation

Many chains need flexibility around MAX_CODE_SIZE, MAX_INITCODE_SIZE, and tx_gas_limit_cap (see reth#21018). This need is validated by EIP-7907.

Currently, configuring these limits requires verbose manual field assignments:

evm_env.cfg_env.limit_contract_code_size = Some(limits.max_code_size);
evm_env.cfg_env.limit_contract_initcode_size = Some(limits.max_initcode_size);
if let Some(cap) = limits.tx_gas_limit_cap {
    evm_env.cfg_env.tx_gas_limit_cap = Some(cap);
}

Solution

Add EvmLimitParams struct and a with_limits() builder method on EvmEnv:

  pub struct EvmLimitParams {
      pub max_code_size: usize,
      pub max_initcode_size: usize,
      pub tx_gas_limit_cap: Option<u64>,
  }

  // Usage:
  let evm_env = EvmEnv::for_eth_block(...).with_limits(limits);

This follows the existing builder pattern used by CfgEnv (e.g., with_chain_id(), with_spec()).

However, a alternative consideration to be made is whether this helper should be configured in revm directly, similar to helpers like below

    pub fn with_max_blobs_per_tx(mut self, max_blobs_per_tx: u64) -> Self {
        self.set_max_blobs_per_tx(max_blobs_per_tx);
        self
    }

PR Checklist

• Added Tests
• Added Documentation
• Breaking changes -> None

[mattsse]

tiny suggestion

[mattsse]

this will likely be a bit inconvenient to manage because we also need this dep in the chainspec

but turns out we already have that in there

[mattsse]

we should not unwrap here and instead leave this as is so that we respect the none value properly