Use OpBlockExecutionError in op execution

[emhane]

Describe the feature

Reveres relationship between op error and L1 error. The L1 error can occur on L2, hence it makes more sense to wrap it in the OP error, as opposed to converting the OP error to BlockExecutionError::Other and thereby loosing important type info.

Add variant OpBlockExecutionError::Eth that wraps a BlockExecutionError. Remove conversion from OpBlockExecutionError to BlockExecutionError.

reth/crates/optimism/evm/src/error.rs

Lines 6 to 30 in 9b44e2a

	/// Optimism Block Executor Errors
	#[derive(Debug, Clone, PartialEq, Eq, thiserror::Error)]
	pub enum OpBlockExecutionError {
	/// Error when trying to parse L1 block info
	#[error("could not get L1 block info from L2 block: {message}")]
	L1BlockInfoError {
	/// The inner error message
	message: String,
	},
	/// Thrown when force deploy of create2deployer code fails.
	#[error("failed to force create2deployer account code")]
	ForceCreate2DeployerFail,
	/// Thrown when a blob transaction is included in a sequencer's block.
	#[error("blob transaction included in sequencer block")]
	BlobTransactionRejected,
	/// Thrown when a database account could not be loaded.
	#[error("failed to load account {_0}")]
	AccountLoadFailed(alloy_primitives::Address),
	}
	impl From<OpBlockExecutionError> for BlockExecutionError {
	fn from(err: OpBlockExecutionError) -> Self {
	Self::other(err)
	}
	}

Update op execution to use OpBlockExecutionError

reth/crates/optimism/evm/src/execute.rs

Line 129 in 9b44e2a

type Error = BlockExecutionError;

Additional context

No response

[chungquantin]

Can I work on this?

[chungquantin]

Created a PR #13696 to tackle this issue but need opinions from core devs for additional progress on the PR.