Cardano Updates

The info banner sat inside the genesis() function body, so it fired once per `wb genesis <op>` dispatch

Era was previously inferred from .era inside profile.json. Promote it to a first-class workbench-level input.

cardano-profile recognises the pparamsEpoch values that target PV 11 and adds a dijkstra zero stub and a v11-preview overlay so profiles can opt in.

Remove the "genesis spec" workbench command that was used for `create-testnet-data --spec-*` and instead use what cardano-profile provides.

The profile may have null "conway" or "dijkstra" genesis fields, but the node still needs valid files. Use a "zero" genesis in those cases.

Based on a mainnet db-sync and mainnet genesis files, reconstruct the timeline without baking in cardano-profile-specific assumptions.

Going forward, the only way to inject cost models with any number of parameters is through Alonzo genesis "extraConfig" field.

- Structure: cost models are separated from the rest of the parameters.
- Consistency: Shelley genesis is the full object, not only the "protocolParams" field.
- Consistency: cost models are an object everywhere, no arrays.
- Cost model names are updated.

These cost models were removed when the node started accepting only what mainnet shipped with.

The pool relays written into the Shelley genesis (via `pool-relays.json` and `cardano-cli ... --relays` / `--relay-specification-file`) are only consumed by ledger-peer discovery.

With ledger peers off and `publicRoots` empty, the relay records in genesis are never read.

Every workbench topology disables it:
- the supervisor (local / 127.0.0.1) backend gets `useLedgerAfterSlot: -1` from `cardano-topology projection-for`.
- the Nomad backend hardcodes the same value (nix/workbench/backend/nomad-job.nix).

Was converging to `create-staked` output, keep `create-testnet-data` layout:
- pools-keys/poolN/{cold,kes,vrf,opcert}.{skey,vkey,cert,counter}
- stake-delegators/delegatorN/{payment,staking}.{skey,vkey}
- drep-keys/drepN/drep.{skey,vkey}
- utxo-keys/utxoN/utxo.{skey,vkey}
- genesis-keys/genesisN/key.{skey,vkey}
- delegate-keys/delegateN/{key,kes,vrf,opcert}.{skey,vkey,cert,counter}
- byron-gen-command/

Normalises genesis file names. Every era's genesis file is now genesis.<era>.json everywhere:
- genesis.byron.json
- genesis.shelley.json
- genesis.alonzo.json
- genesis.conway.json
- genesis.dijkstra.json

Details:
- create-testnet-data drops its symlink-creation block and the `link_keys` helper (no longer needed under the native layout).
- Removes `Massage_the_key_file_layout_to_match_AWS`, `key_depl` and `key_genesis`.

The names `create-testnet-data` itself emits are unchanged and the workbench's downstream consumers are updated to read the normalised form.

Replaces 'cardano-cli byron genesis genesis'.

This introduces changes to the cache output so the directory entry now has the "v2" suffix.

Removes genesis-byron-{jq,modular} and the genesis-byron dispatcher.

`create-testnet-data` is now the only supported path.

Move the preset-dispatch branch out of the per-call helpers so the "from preset" path is resolved once at source time,
matching the other backend-dispatch consolidations.

Function `derive-from-cache` becomes a backend implementation.

Both `derive-from-cache` and `finalise-cache-entry` are merged and inlined into `derive-from-cache-jq` (`derive-from-cache-modular` delegates to "jq").

Resolve `$genesis_backend` once at source time and replace all the 'if WB_MODULAR_GENESIS' with a single `"X-$genesis_backend" "$@"`.

Applies to `profile-cache-key-input`, `profile-cache-key`, `spec` and `pool-relays`.

Also, the decision between `create-testnet-data` and `create-staked` (WB_CREATE_TESTNET_DATA), now lives in the "jq" backend
(the "modular" backend only implements spec, pool-relays, byron and cache key functions, not the create-testnet-data call).

Both genesis backends, "jq" and "modular", now live in the same file. Extract unmodified the code of each to new files.

The bound was too tight and sometimes we could not fulfill the contract that the
Dynamo was honest. The cause for re-download is now noted and in case the dynamo
is adversarial we allow for some more re-downloads.

Bundling it into the tar doubled the upload

Rework the snapshot-converter into a command tree:

  - daemon:  watch a node's snapshot directory and convert each exported LSM
             snapshot into a Mem snapshot as it is produced
  - convert: one-shot conversion between an exported LSM snapshot and a Mem
             snapshot, in either direction
  - lsm export / lsm import: move snapshots out of / into an offline LSM
             database

Conversions operate only on standalone (exported) LSM snapshots and Mem
snapshots, never on a live database.

db-analyser surfaces the LSM snapshot export directory via a new 'mkLSMConfig'
method on 'HasProtocolInfo' (read from the node config's
'LedgerDB.LSMExportPath').