feat(rpc): relax VaidationApi and EngineApi

[klkvr]

Based on #13232

Relaxes bounds for ValidationApi and EngineApi, migrating all of the RPC setup off the concrete primitives.

Changes:

• Block AT and ensure_well_formed_payload method are extracted from EngineValidator into a separate PayloadValidator which can be used to validate ExecutionPayloads without the need to know entire EngineTypes
• Arc<dyn PayloadValidator> is stored on rpc builder and rpc registry, and passed to ValidationApi to abastract the ExecutionPayload -> Block conversion. I didn't make it a generic because this would require adding an additional generic to RpcRegistry and all types that hold it including user-facing RpcHandle

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

  Lines 192 to 206 in 8f98b0f

  	/// Helper wrapper type to encapsulate the [`RpcRegistryInner`] over components trait.
  	#[derive(Debug, Clone)]
  	#[allow(clippy::type_complexity)]
  	pub struct RpcRegistry<Node: FullNodeComponents, EthApi: EthApiTypes> {
  	pub(crate) registry: RpcRegistryInner<
  	Node::Provider,
  	Node::Pool,
  	Node::Network,
  	TaskExecutor,
  	Node::Provider,
  	EthApi,
  	Node::Executor,
  	Node::Consensus,
  	>,
  	}

  
  A one way we could consider simplifying this is require users to implement engine validation traits directly on Consensus. This feels semantically right and should also allow make it easier to support nodes without engine

[mattsse]

makes sense, lgtm!