Move cfg_env and block_env configuration from PayloadBuilderAttributes into PayloadBuilder

[garwahl]

This PR moves the configuration environment and block environment setup from PayloadBuilderAttributes out into their respective payload builders.

Context
Both OptimismPayloadBuilder and EthereumPayloadBuilder have an evm_config that defines a fill_cfg_and_block_env that we can use to populate.

This closes #10446 which has additional context.

[garwahl]

I don't have enough context to meaningfully update this comment so please suggest alternatives.

[garwahl]

@mattsse @onbjerg PTAL.

I am still fixing imports etc due to /crates/optimism/ not importing correctly into my VSCode but I will fix that in parallel as this gets reviewed.

[garwahl]

Hey @mattsse @onbjerg one thing I'd love some guidance on is now that initialized_block_env and initialized_cfg have been removed from PayloadConfig

reth/crates/payload/basic/src/lib.rs

Lines 676 to 679 in a942467

	/// Pre-configured block environment.
	pub initialized_block_env: BlockEnv,
	/// Configuration for the environment.
	pub initialized_cfg: CfgEnvWithHandlerCfg,

Both the OptimismPayloadBuilder and EthereumPayloadBuilder require these. I assume a good place to move these fields would be to OptimismPayloadBuilderAttributes and EthPayloadBuilderAttributes respectively, unless there is somewhere better/shared?

[garwahl]

ping @mattsse would love your thoughts here

[mattsse]

I realized we need to do some additional changes first so we can easily do this

[mattsse]

@onbjerg I removed the cfg_and_block_env from the trait and instead moved this into the payloadbuilder impl.

this isn't perfect yet, because ideally we can use the evmconfig for this entirely, but this is currently tricky because we'd need to construct the new header right away

[onbjerg]

can work with this in alphanet for now

[garwahl]

Thanks for getting this across the line @mattsse @onbjerg much appreciated