Move RethModuleRegistry functionality into RpcRegistry

[emhane]

Describe the feature

Move RethModuleRegistry functionality into RpcRegistry, which is rn a wrapper around RethModuleRegistry.

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

Lines 148 to 159 in e90b526

	/// Helper wrapper type to encapsulate the [`RethModuleRegistry`] over components trait.
	#[derive(Debug)]
	pub struct RpcRegistry<Node: FullNodeComponents> {
	pub(crate) registry: RethModuleRegistry<
	Node::Provider,
	Node::Pool,
	NetworkHandle,
	TaskExecutor,
	Node::Provider,
	Node::Evm,
	>,
	}

Additional context

No response

[tcoratger]

@emhane Here a few questions:

• Do you plan to keep the RethModuleRegistry structure inside the rpc builder and just migrate all the features or do you also plan to completely remove RethModuleRegistry?
• If we want to delete RethModuleRegistry then we must also migrate the RpcModuleBuilder to the node builder and as on the node builder we have an implementation constraint which is Node: FullNodeComponents, then we will no longer be able to keep RpcModuleBuilder as generic as it is now. I am thinking in particular of the default() function which could no longer work as it currently does.

[emhane]

@emhane Here a few questions:

• Do you plan to keep the RethModuleRegistry structure inside the rpc builder and just migrate all the features or do you also plan to completely remove RethModuleRegistry?
• If we want to delete RethModuleRegistry then we must also migrate the RpcModuleBuilder to the node builder and as on the node builder we have an implementation constraint which is Node: FullNodeComponents, then we will no longer be able to keep RpcModuleBuilder as generic as it is now. I am thinking in particular of the default() function which could no longer work as it currently does.

goal is to follow payload or pool builder pattern, but this issue is blocked rn, would be nice if you can pick up any other 🙏