Cardano Updates

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

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

bench: remove cardano-recon-framework

bench: remove cardano-recon-framework

  Adapts cardano-node to the updated ouroboros-consensus
  newLeiosDBSQLite signature (Tracer IO TraceLeiosDb -> FilePath -> ...)
  from IntersectMBO/ouroboros-consensus#2062 by contramapping the
  TraceLeiosDb constructor into the existing Consensus.LeiosKernel
  tracer. SQLite UNIQUE/PRIMARY KEY collision events are given Warning
  severity so they remain visible under the default Notice configuration.

Co-Authored-By: Claude Fable 5 <[email protected]>

Adapts cardano-node to the updated ouroboros-consensus
newLeiosDBSQLite signature (Tracer IO TraceLeiosDb -> FilePath -> ...)
introduced in IntersectMBO/ouroboros-consensus#2062, and surfaces the
SQLite UNIQUE/PRIMARY KEY collision events it emits.

* New tracing: adds a leiosDbTracer field on Cardano.Node.Tracing.Tracers,
  wires it via mkCardanoTracer at namespace Consensus.LeiosDb, and provides
  LogFormatting / MetaTrace instances (Warning severity).
* Legacy tracing: leiosDbTracer = nullTracer, matching how the other
  Leios consensus tracers are currently left.
* Run.hs: passes (leiosDbTracer tracers) to newLeiosDBSQLite.

Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>

cardano-node: remove iohk-monitoring tracing backend

`run-node` and `run-tracer` wrote a sourceable env file to `/usr/local/bin/env` at
every startup, which fails under `--read-only` / `readOnlyRootFilesystem`. The
file was introduced in d9c8317e5 (#2801) to feed the topologyUpdate script added the same day in
c652f1055. topologyUpdate was removed in 56266c061 and never reintroduced;
the writer was preserved by accident when 34a4796ed re-created the docker
context, along with a stale `# Mapping for topologyUpdater` comment. Across
all branches, there is noconsumer besides the deleted topologyUpdater.

The `CARDANO_*` snapshot remains useful for operators that exec into the
container and want the resolved (post-defaults) config in a shell, so the
writer is kept but redirected to `/tmp/cardano-env` (writable when `/tmp` is
mounted as tmpfs/emptyDir). A build-time symlink at `/usr/local/bin/env ->
/tmp/cardano-env` keeps the legacy path resolving in case any out-of-tree
consumer depends on it.

The variables that existed only for topologyUpdater are dropped from the
snapshot.

The README's new "Read-Only Root Filesystem" section documents the required
writable mounts, the new env-snapshot path, and how custom-mode operators
should direct any profile output to a writable mount.

In response to #6470.

The cardano-node and cardano-tracer service modules unconditionally emitted
`--machine-readable -tcardano-node.stats -pocardano-node` in the default
`profilingArgs`, regardless of `cfg.profiling`. GHC's `-tFILE` always writes the
stats file on shutdown, which broke startup on read-only filesystems even
though no profiling was configured. Gate the three flags on
`cfg.profiling != "none" || cfg.eventlog` so the default RTS command line is
empty when nothing is requested.

When profiling is enabled, the same flags now consult a new option,
`services.cardano-node.profilingOutputDir` (and the tracer equivalent), to
prefix the output file paths. The option defaults to null, preserving today's
relative-path behavior on NixOS where systemd's `WorkingDirectory` equals
`cfg.stateDir`. `scripts.nix` sets it to `/logs` for the OCI script wrappers, so
profile output under the read-only OCI image lands on the writable `/logs`
mount.

In response to #6470.

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.