Promote Rpc to a node component

[mattsse]

this part is slightly confusing:

reth/crates/node/api/src/node.rs

Lines 94 to 110 in e7defb2

	/// Returns the builder for type.
	pub trait BuilderProvider<N: FullNodeComponents>: Send {
	/// Context required to build type.
	type Ctx<'a>;
	/// Returns builder for type.
	#[allow(clippy::type_complexity)]
	fn builder() -> Box<dyn for<'a> Fn(Self::Ctx<'a>) -> Self + Send>;
	}
	impl<N: FullNodeComponents> BuilderProvider<N> for () {
	type Ctx<'a> = ();
	fn builder() -> Box<dyn for<'a> Fn(Self::Ctx<'a>) -> Self + Send> {
	Box::new(noop_builder)
	}
	}

this is more like a helper trait to create the ethapi component.

atm the rpc is not stateful:

reth/crates/ethereum/node/src/node.rs

Lines 76 to 82 in e7defb2

	/// Add-ons w.r.t. l1 ethereum.
	#[derive(Debug, Clone)]
	pub struct EthereumAddOns;
	impl<N: FullNodeComponents> NodeAddOns<N> for EthereumAddOns {
	type EthApi = EthApi<N::Provider, N::Pool, NetworkHandle, N::Evm>;
	}

we should make this stateful similar to a trait RpcBuilder, like we do with:

reth/crates/ethereum/node/src/node.rs

Lines 89 to 96 in e7defb2

	type ComponentsBuilder = ComponentsBuilder<
	N,
	EthereumPoolBuilder,
	EthereumPayloadBuilder,
	EthereumNetworkBuilder,
	EthereumExecutorBuilder,
	EthereumConsensusBuilder,
	>;

this way the rpc setup can be customized entirely, not only the ethapi part.

this also allows us to separate engine server setup from regular rpc.

First we can make the Addons stateful

[emhane]

ref #8987

[github-actions]

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

[mattsse]

with #11532 we now have this