Cardano Updates

Additive-then-remove strategy: add ledger-native paths alongside
cardano-api, migrate consumers one module at a time (each commit
compiles), then atomically remove cardano-api in a single commit.

51 tasks across 5 phases (A-E). Covers pin bump, new type paths,
consumer migration, atomic removal, and verification.

Centralise crypto deps behind Cardano.Address.Crypto

Co-authored-by: Alexey Kuleshevich <[email protected]>

Superseded by the rework of the snapshot policy for predictable snapshots, with
dedicated new tests

LedgerDB: implement predictable snapshotting

This commit brings back the fix from https://github.com/IntersectMBO/ouroboros-consensus/pull/1814, which synchronises the process of taking a ledger state snapshot and copying of blocks into the immutable DB.

- tryTakeSnapshot: now accepts a `Time` argument. The argument specifies the time at which the snapshot should be taken
- LedgerDBEnv: rename ldbLastSnapshotWrite to ldbLastSnapshotRequestedAt. Track the request time rather than the time a snapshot actually finished.
- implTryTakeSnapshot: add a `delay` argument. How long should we block before actually taking the snapshot after determining the slots to snapshot
- add `cdbSnapshotDelayRNG` and use this to determine how long we should wait before taking a snapshot
- add orphan `NoThunks` `StdGen` instance
- add `cdbsSnapshotDelayRNG to `ChainDbSpecificArgs`
- add `onDiskSnapshotDelayRange` to `SnapshotPolicy` to allow configuration of the delay between a snapshot being requested and being taken
- add LedgerDB snapshot delay trace events. Use these events in the test suite to ensure we don't add blocks while snapshots are occurring (and therefore make an accurate number of snapshots).
- add a test ensuring that blocks can be added while a snapshot is enqueued
- ledgerDbMaintenaceThread -> ledgerDbMaintenanceThread

It is no longer needed by the predictable snapshotting logic.