feat: integrate NodeTypesWithDB

[klkvr]

following #10683 integrates NodeTypesWithDB for use in providers and to types depending on them.

This introcuces a lot of ChainSpec = ChainSpec bounds comming from concrete provider implementations. I've created a helper trait ProviderNodeTypes

reth/crates/storage/provider/src/providers/mod.rs

Line 64 in 12b5d45

pub trait ProviderNodeTypes: NodeTypesWithDB<ChainSpec = ChainSpec> {}

this trait can be removed/relaxed once we figure out requirements for abstracted chainspec

[onbjerg]

not clear to me why we need the full node types here?

[klkvr]

basically it's needed because pipeline currently depends on concrete ProviderFactory which needs chainspec AT

we can indeed avoid this by doing <DB, Provider: DatabaseProviderFactory<DB> + ...>, but given that we're going to make providers generic over primitive types this DB generic would at some point become NodeTypesWithDB or equivalent anyway

[mattsse]

very nice,

granted this introduces additional verbosity, but this is necessary if we want to integrate type generics on provider/db level

there are def some simplifications we can when it comes to the NodeWith trait, but imo it's nice to group db+types in on trait and the caller is responsible to instantiate this
the nice benefit of this is that we can get rid of a ton of DB generics, which is nice.
we also only can use the DB together with types so it makes sense to group those imo.

followup simplifications we can try are

• stacked trait bounds for engine, this requires some nodebuilder changes which we def need to do
• move away from ChainSpec as the default type