Introduce EngineApiKind

[mattsse]

There are certain OPstack differences in the engine API

such as

reth/crates/consensus/beacon/src/engine/mod.rs

Lines 459 to 461 in 08158e4

	// On Optimism, the proposers are allowed to reorg their own chain at will.
	#[cfg(feature = "optimism")]
	if self.blockchain.chain_spec().is_optimism() {

reth/crates/consensus/beacon/src/engine/mod.rs

Lines 693 to 706 in 08158e4

	// OPTIMISTIC SYNCING
	//
	// It can happen when the node is doing an
	// optimistic sync, where the CL has no knowledge of the finalized hash,
	// but is expecting the EL to sync as high
	// as possible before finalizing.
	//
	// This usually doesn't happen on ETH mainnet since CLs use the more
	// secure checkpoint syncing.
	//
	// However, optimism chains will do this. The risk of a reorg is however
	// low.
	debug!(target: "consensus::engine", hash=?state.head_block_hash, "Setting head hash as an optimistic pipeline target.");
	return Some(state.head_block_hash)

but overall the engine API impl is more or less the same so we can introduce these conditional checks by introducing an enum like

enum EngineApiKind {
  Ethereum,
  OpStack
}

[github-actions]

This issue is stale because it has been open for 21 days with no activity.