Feat: Sync directly from Reth and/or its database

[jmcph4]

Describe the feature you would like

Syncing a checkpoint directly from Reth. This comes in two flavours:

• Syncing in-process with Reth,
• Syncing from the Reth database, via a DatabaseProviderRO

Motivation

The overarching motivation here is that, assuming that one has access to a working Reth node, we already have the necessary information to both populate and synchronise any pools that we need -- we should not have to reserialise nor incur the performance penalties associated with communication via the network stack.

As above, there are two cases:

• In-process (i.e., via the NodeBuilder API),
• Database (i.e., via the filesystem, through the aforementioned DatabaseProviderRO API)

Additional context

Currently, all of the checkpoint syncing APIs accept an Alloy Provider, which can only abstract over HTTP, Websocket, or IPC (a la Unix sockets) transports.

[jmcph4]

There are two angles of attack in my opinion:

• Somehow obtain an Alloy Provider from the Reth SDK,
• Wrap an Alloy Provider with an analogous Reth type (FullRpcProvider?) either via
  • A new trait, say BlockchainDataProvider (bad name, I admit)
  • A newtype struct or enum

Would love feedback from essentially anyone but particularly @0xKitsune or @0xOsiris.