Add --store-ledger option to db-analyser

[EncodePanda]

Consider a chain downloaded by cardano-node. While getting the chain, the default disk policy created two snapshots on disk

$> ls -h db_mainnet/ledger
13916582  14776127

Now we can ask db-analyser to also create a snapshot of ledger at slot 13916582 - while processing the chain - and store it. The name of the file will be 13916582_db-analyser.
(please note that by providing a suffix _db-analyser we ensure that the snapshot will not be deleted by node in the future)

cabal run ouroboros-consensus-cardano:db-analyser --  \
  --db db_mainnet cardano \
  --configByron dbacfg/mainnet-byron-genesis.json \ 
  --configShelley dbacfg/mainnet-shelley-genesis.json \
  --nonce 1a3be38bcbb7911969283716ad7aa550250226b76a61fc51cc9a9a35d9276d81 \
  --configAlonzo dbacfg/mainnet-alonzo-genesis.json \
  --store-ledger 13916582

Once the node is done with its work we can see that the snapshot is created.

ls -h db_mainnet/ledger
13916582  13916582_db-analyser  14776127

We can now compare if snapshot created by node is identical to the one created by db-analyser

&> cmp db_mainnet/ledger/13916582 db_mainnet/ledger/13916582_db-analyser \
&& echo 'success' || echo 'failure'

success

[EncodePanda]

I've just finished running the tool against longer chain that also holds alonzo blocks, and everything works as expected

λ cmp db_mainnet_with_alonzo_40217333/ledger/40174168 db_mainnet_with_alonzo_40217333/ledger/40174168_db-analyser && echo 'success' || echo 'failure'

success

[dnadales]

• what is hasFS set to, and does it make sense to always have a value?
• can we avoid exposing new symbols in OnDisk
• would it make sense to rename storeLedgerX functions to storeLedgeStateAt?
• shouldn't snapshot taking stop at the specified slot number?

[dnadales]

Approved after discussing my comments with Pawel.

[EncodePanda]

bors merge

[iohk-bors]

Build succeeded:

• ci/hydra:Cardano:ouroboros-network:required
• buildkite/ouroboros-network