Move network setup code from node-core to node-builder launch/ BuilderContext types

[mattsse]

Describe the feature

currently the NodeConfig type contains various helpers for setting up the network

reth/crates/node-core/src/node_config.rs

Line 309 in 36c8f36

pub async fn build_network<C>(

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

Lines 561 to 572 in 36c8f36

	/// Creates the [NetworkBuilder] for the node.
	pub async fn network_builder(&self) -> eyre::Result<NetworkBuilder<Node::Provider, (), ()>> {
	self.config
	.build_network(
	&self.reth_config,
	self.provider.clone(),
	self.executor.clone(),
	self.head,
	self.data_dir(),
	)
	.await
	}

which is used as convenience fn during NetworkBuilder:

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

Line 197 in 36c8f36

let network = ctx.network_builder().await?;

with the new launch types, I think we can simplify this and ideally remove the network code from node-core

the entrypoint is here:

reth/crates/node/builder/src/launch/mod.rs

Lines 155 to 166 in 36c8f36

	let builder_ctx = BuilderContext::new(
	head,
	blockchain_db.clone(),
	ctx.task_executor().clone(),
	ctx.data_dir().clone(),
	ctx.node_config().clone(),
	ctx.toml_config().clone(),
	evm_config.clone(),
	);
	debug!(target: "reth::cli", "creating components");
	let components = components_builder.build_components(&builder_ctx).await?;

TODO

• move network related code to BuilderContext, we can probably change a few things in BuilderContext, for example using this type

reth/crates/node/builder/src/launch/common.rs

Lines 450 to 458 in 36c8f36

	/// Helper container type to bundle the initial [NodeConfig] and the loaded settings from the
	/// reth.toml config
	#[derive(Debug, Clone)]
	pub struct WithConfigs {
	/// The configured, usually derived from the CLI.
	pub config: NodeConfig,
	/// The loaded reth.toml config.
	pub toml_config: reth_config::Config,
	}

Additional context

No response