Move more provider traits into storage-api crate

[mattsse]

Describe the feature

we still have a few traits defined in the reth-provider crate that are independent of reth-provider internals, like

reth/crates/storage/provider/src/traits/history.rs

Line 10 in e6a6fc4

pub trait HistoryWriter: Send + Sync {

all of those should be moved to

reth/crates/storage/storage-api/Cargo.toml

Line 2 in e6a6fc4

name = "reth-storage-api"

ideally, trait by trait to make review easy.
can be re-exported from reth-provider to not break a ton of stuff

Additional context

No response

[PanGan21]

Hi @mattsse started with #12480 and I can continue on this depending on the recommended length of each pr!

[mattsse]

cool, ty!

[PanGan21]

Which other traits do you think are relevant to this task?

[mattsse]

this one we can move as well

reth/crates/storage/provider/src/traits/header_sync_gap.rs

Line 31 in cef7ec8

pub trait HeaderSyncGapProvider: Send + Sync {

[PanGan21]

I had a look again on this and it seems it is used here:

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

Line 1202 in cef7ec8

impl<TX: DbTx + 'static, N: NodeTypes> HeaderSyncGapProvider for DatabaseProvider<TX, N> {

Do you still consider that it should be moved to storage-api crate?

[mattsse]

hmm, actually not sure about this one because this is kinda p2p, so we can keep this particular one for now

[PanGan21]

hmm, actually not sure about this one because this is kinda p2p, so we can keep this particular one for now

Cool. What else do you think is necessary to resolve this ticket?