Add EngineApiBuilder to RpcAddons

[emhane]

Describe the feature

Define EngineApiBuilder and add to RpcAddons. Follow how it has been done for EthApiBuilder and EngineValidator

reth/crates/node/builder/src/rpc.rs

Lines 338 to 341 in 7e972ea

	/// Builder for `EthApi`
	eth_api_builder: Box<dyn FnOnce(&EthApiBuilderCtx<Node>) -> EthApi + Send + Sync>,
	/// Engine validator
	engine_validator_builder: EV,

Then, instead of calling EngineApi constructor here, call EngineApiBuilder::build

reth/crates/node/builder/src/rpc.rs

Lines 435 to 445 in 7e972ea

	let engine_api = EngineApi::new(
	node.provider().clone(),
	config.chain.clone(),
	beacon_engine_handle,
	PayloadStore::new(node.payload_builder().clone()),
	node.pool().clone(),
	Box::new(node.task_executor().clone()),
	client,
	EngineCapabilities::default(),
	engine_validator.clone(),
	);

Additional context

No response

[mattsse]

if we need to modify engine api then this should become part of the launch logic I think

[emhane]

not sure I follow? rn this trait isn't used, implementing this issue would make way for using it
https://github.com/alloy-rs/op-alloy/blob/b506e16d6e6bb0f3cf416c965092b693fea4cb71/crates/provider/src/ext/engine.rs#L13-L180

[klkvr]

@emhane isn't this trait only relevant for alloy provider and not reth rpc? i.e op-node would still expect eth-compatible engine API

[emhane]

@klkvr https://specs.optimism.io/protocol/exec-engine.html#engine-api

[emhane]

@cody-wang-cb are you keen on this to unblock ethereum-optimism/pm#20

[mattsse]

unclear what this is issue is about tbh

what's the usecase here

[emhane]

actually op Engine API shouldn't support v1 requests, it breaks spec. eventually we want to use the op_alloy_provider::OpEngineApi in op-reth. to do so, an Engine API builder must be exposed at sdk level.

ref https://specs.optimism.io/protocol/exec-engine.html