Cardano Updates

Publishes the current state of programmatic access to Antithesis test
reports: no REST API or MCP server, reports arrive as signed HTML URLs
via email, and the official path for AI-agent triage is the
antithesis-triage skill plus snouty/agent-browser/jq.

Adds docs/triage.md with the full story and how it ties into the moog
workflow we use to request and decrypt report URLs.

refactor: remove DREP and STAKE deposit constants from codebase

Adds a transaction generator (Python, continuously submits splits/consumes
to grow the UTxO set) via relay1, and Ogmios as an N2C client via relay2.

- tx-generator component with Dockerfile and Python script
- n2c-harness to convert SIGTERM to SIGINT for GHC-based N2C clients
- configurator preserves UTxO keys to /utxo-keys for tx-generator funding
- relay1 gets a named state volume so tx-generator can read its node socket
- relay2 gets a named state volume so Ogmios can read its node socket
- configurator image bumped to tx-gen-v1 which bundles Nix store for deps

Kupo is intentionally excluded — it failed Antithesis in bisection while
tx-gen and Ogmios passed individually.

chore: remove repetitive word in comment

fix #2579 #2562 


- Add `retryOnBlockfrostError` helper with exponential backoff (1s→60s
cap, max 10 retries) for our own `APIBlockfrostError` variants
(`DecodeError`, `MissingNextBlockHash`, `MissingBlockNo`, etc.)
- Wrap `catchUpToLatest` in the retry helper so transient errors during
chain catch-up don't crash the node
- Make `DecodeError` retryable (was previously fatal) since partial HTTP
responses can cause transient CBOR decode failures
- Blockfrost API errors (timeouts, rate limits, 5xx) will be handled by
the upstream client library (see
[blockfrost-haskell#88](https://github.com/blockfrost/blockfrost-haskell/pull/88))


~NOTE: Do not merge until
https://github.com/blockfrost/blockfrost-haskell/pull/88 is merged and
the BF version is updated in hydra-node.~ ( Edit: @noonio - it's merged
now and I've updated the versions. )

<!-- Consider each and tick it off one way or the other -->
* [x] CHANGELOG updated or not needed
* [x] Documentation updated or not needed
* [x] Haddocks updated or not needed
* [x] No new TODOs introduced or explained herafter

This commit implements a generic interface that can be used to
instantiate multiple voting committee schemes using multiple crypto
backends for vote and certificate signing and validation.

The main CryptoSupportsVotingCommittee type class allows implementations
to define abstract votes and certificate types, check when a node should
vote, and forge and verify certificates and votes.

In addition, it provides a wrapper that allows us to keep track of two
simultaneous voting committees, the one corresponding to the current
epoch, and the one from the previous one. This is needed to validate
votes and certificates arriving slightly late at the beginning of a new
epoch.

Co-authored-by: Nicolas BACQUEY <[email protected]>
Co-authored-by: Thomas BAGREL <[email protected]>
Co-authored-by: Agustin Mista <[email protected]>

Co-authored-by: Nicolas BACQUEY <[email protected]>
Co-authored-by: Thomas BAGREL <[email protected]>
Co-authored-by: Agustin Mista <[email protected]>

10.7.1 upgrade

Fix syntax error in simple_mixed_consensus

Update all target to report failing testnets.

Have cardano-nodes depend on having the gateway nodes started in fancy
topologies.