feat: reuse reth default_ethereum_payload for Ethereum

[SkandaBhat]

Fixes #76.

Notable changes

• Require a state provider factory for all build_payload APIs so builders can fetch parent-scoped state correctly.
• Added a convenience alias pub type ProviderFactory<P> = Arc<dyn traits::ProviderFactoryBounds<P>> to standardize the factory type across call sites.
• Moved the state_by_block_hash lookup into BlockContext::new so payload construction always uses the parent block’s state.

[julio4]

I guess this works but it would be better to not have to store the factory in the block context. We already have all the information we need in the base state to build the payload.

But if there's no other easy ways to do it then this is good!

[SkandaBhat]

@julio4 One other approach is to wrap the base_state provider in a StateProviderFactory + ChainSpecProvider wrapper right before calling default_ethereum_payload so we don’t have to carry the factory around. The tradeoff is increased surface area inside ethereum module since we need to maintain implementations for StateProviderFactory (latest, pending etc)

[julio4]

@julio4 One other approach is to wrap the base_state provider in a StateProviderFactory + ChainSpecProvider wrapper right before calling default_ethereum_payload so we don’t have to carry the factory around. The tradeoff is increased surface area inside ethereum module since we need to maintain implementations for StateProviderFactory (latest, pending etc)

Yes agree, I tried this before but wasn't convinced. I think your solution looks nice for the time being!

[SkandaBhat]

Clippy fails because of latest rust version 1.92 changing the rules. Fixed it in #100