Cardano Updates

And adapt Cardano related test extensions.

Signed-off-by: Aaravanand00 <[email protected]>

Signed-off-by: Chris Gianelloni <[email protected]>

Signed-off-by: Aaravanand00 <[email protected]>

Replace mkUnsignedTx + mkByronWitness/mkShelleyWitness with
mkLedgerTx + mkByronWitnessLedger/mkShelleyWitnessLedger in
the duplicated test module.

All 8 golden hex string tests pass — ledger-native construction
produces byte-identical CBOR to the cardano-api construction.

Signed-off-by: Aaravanand00 <[email protected]>

Bumps [github.com/jackc/pgx/v5](https://github.com/jackc/pgx) from 5.9.0 to 5.9.2.
- [Changelog](https://github.com/jackc/pgx/blob/master/CHANGELOG.md)
- [Commits](https://github.com/jackc/pgx/compare/v5.9.0...v5.9.2)

---
updated-dependencies:
- dependency-name: github.com/jackc/pgx/v5
  dependency-version: 5.9.2
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <[email protected]>

The trace messages that get emitted differ between debug and release
builds. Therefore, running the same test (with the same golden file of
expected trace messages) both for debug and release builds will cause
problems. To avoid these, we now have two separate tests, each with its
own golden file, and only run the appropriate one depending on the build
type.

The only reason this did not lead to problems so far is that the test
only inserted four entries into the table, not triggering any
interesting internal events. However, we *will* emit internal messages
once we start migrating the union level when a union is paid off (or we
decide to test more interesting operations). Since we now can, I made
sure that these tests now at least trigger the creation of a merge.

Signed-off-by: Bhargav Dabhade <[email protected]>

The tracing messages that get emitted differ between debug and release
builds. Therefore, running the same test (with the same golden file of
expected tracing messages) both for debug and release builds will cause
problems. To avoid these, we now have two separate tests, each with its
own golden file, and only run the appropriate one depending on the build
type.

The only reason this did not lead to problems so far is that the test
only inserted four entries into the table, not triggering any
interesting internal events. However, we *will* emit internal messages
once we start migrating the union level when a union is paid off (or we
decide to test more interesting operations).

Picks up the instrumented convergence composer built by
publish-images from the preceding commit.

Applies the /antithesis-tests skill to the flagship test. Before, the
cardano_node_master testnet had:

- One no-op serial_driver (sleep 60), inherited from moog with no
  test semantics. Antithesis's 'All commands were run to completion
  at least once' property required it to run on some timeline, which
  it sometimes didn't at duration=1h (~30% flake rate).
- One eventually_ command with a 12-hour polling loop. Antithesis's
  eventually_ is meant to be a short post-fault recovery probe that
  exits quickly. A 12h loop means the script never 'runs to
  completion' in any reasonable duration, double-flagging under
  'started' and 'run to completion' properties.
- No finally_ command at all.
- No SDK assertions anywhere — the report had nothing to score.

After:

- components/sidecar/composer/convergence/helper_sdk_lib.sh
    Sourceable bash emitter for Antithesis's Fallback SDK JSONL.
    Offers sdk_reachable / sdk_unreachable / sdk_sometimes / sdk_always.
    'helper_' prefix → ignored by the composer, usable by siblings.

- components/sidecar/composer/convergence/eventually_converged.sh
    Rewritten per the canonical pattern: sleep 15s to settle after
    fault injection stops, then up to 10×2s retries (35s worst-case
    wall time) querying tip on every producer, exit 0 on
    convergence / 1 on failure. Emits sdk_reachable on entry,
    sdk_sometimes on success, sdk_unreachable on genuine
    non-convergence. Was a 12h polling loop.

- components/sidecar/composer/convergence/finally_tips_agree.sh
    New. Runs after drivers complete naturally. 15s settle + 5×2s
    tip-agreement retries. sdk_always on the final-state invariant:
    every producer agrees on the tip after workload ends. A failing
    sdk_always here means the test created a permanent fork.

- components/sidecar/composer/convergence/serial_driver_tip_agreement.sh
    New. Replaces serial_driver_sleep.sh. Samples tip on every
    producer 3× under active fault injection, emits sdk_sometimes
    whether tips agree or diverge. Real exclusive-access semantics
    (blocks parallel drivers from writing to the chain while
    sampling), and every sample is a reportable data point.

- components/sidecar/composer/convergence/serial_driver_sleep.sh — deleted.

Locally verified: each script runs to completion on a healthy
compose, all three emit well-formed antithesis_assert JSONL, total
wall time eventually=20s / finally=20s / serial=48s on a green
cluster. No timeout wrapper around cardano-cli ping (the sidecar
image is minimal — coreutils + bash + jq — and 'timeout' was
swallowing cardano-cli's stdout).