Cardano Updates

Register both UTxORPC v1alpha and v1beta service implementations on the
same listener. Clients pick which proto package they call; on the wire
the two are entirely separate gRPC services (utxorpc.v1alpha.* vs
utxorpc.v1beta.*), so no routing logic is needed and v1alpha bytes stay
unchanged.

Layout:
- src/serve/grpc/v1alpha/{query,sync,watch,submit}.rs - moved from
  src/serve/grpc/, imports rewritten to explicit pallas v1alpha paths.
- src/serve/grpc/v1beta/{query,sync,watch,submit}.rs - copies with
  imports swapped to v1beta. The only body divergence is in
  v1beta/query.rs read_utxos, where Datum.original_cbor is
  Option<Bytes> rather than Bytes.
- mod.rs: registers eight server impls (4 services x 2 versions) and
  10 file descriptor sets in tonic reflection.

Cargo.toml: bumps pallas to git rev 0da71c2 to pick up v1alpha and
v1beta proto packages and the v1beta::Mapper.

Drive-by: drop unused _mapper field from SubmitServiceImpl, and remove
two stale commented-out blocks in sync.rs.

Bumps [github.com/blockfrost/blockfrost-go](https://github.com/blockfrost/blockfrost-go) from 0.3.0 to 0.4.0.
- [Release notes](https://github.com/blockfrost/blockfrost-go/releases)
- [Commits](https://github.com/blockfrost/blockfrost-go/compare/v0.3.0...v0.4.0)

---
updated-dependencies:
- dependency-name: github.com/blockfrost/blockfrost-go
  dependency-version: 0.4.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

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

* fix: ensure era transitions bump protocol versions

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

* test: run erastests in subtests so they can run in parallel against the same nodes

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

---------

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

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

The publish-images.sh script resolves the compose tag as a *downstream*
git ref (it git-clones cardano-node-antithesis and checks out that
commit, then builds tx-generator from components/tx-generator/ at that
commit, with whatever upstream pin its flake.nix has).

Bumping the tag to '711eb22' (the upstream SHA) made the script fail:
  Error: Tag '711eb22' not found in repo. Skipping tx-generator.

Fix: point to commit 05e6926 which is the downstream commit that bumps
the flake.nix pin to upstream 711eb22.

Picks up:
  * PR #118 — same duplicate-submit recovery shape applied to the
    transact arm

Targets the second finding from the post-#117 Antithesis run on commit
247a781 (session efe17477e94dfcef7503548edab28ecd-50-7):
'tx_generator_transact_submit_rejected' fired 4x with reason
'All inputs are spent. Transaction has probably already been included'.
Same root cause as the refill bug PR #115/#116/#117 fixed, now in the
transact path.

Local 60s-epoch repro showed bootstrap-producer's 'tool-error: convert'
(exit 6, e.g. 'produced 2 .cbor files, need at least 3') and
'tool-error: nonces' (exit 8) bubbling through to the case * arm,
causing the relay container to exit and rely on restart: always to
retry. The container restart loop works but burns RestartCount and
adds startup latency; the inner script can absorb these transient
failures the same way it absorbs 1/2/5/7 from cluster-not-ready and
extract.

Per /code/amaru-bootstrap/scripts/bootstrap-producer.sh exit-code
registry: 6 = convert tool error (snapshot count too low / convert
failed), 8 = nonces tool error (jq tail rewrite failed). Both transient
under fault injection or short chains.

While iterating on the tx-generator daemon's reconnect resilience the
asteria-stub workload's 'stub heartbeat ticked' Sometimes assertion
fires under fault injection (its own indexer goes
indexer_unresponsive=true / connection-refused during a relay restart)
and surfaces as a finding alongside the tx-generator findings we are
actually triaging. That obscures the signal we care about.

Drop the asteria-stub service + volume on this branch only. Restore
when promoting back to main testnet.

Walked back the sidecar drop. The asteria_game testnet is
cardano_node_master + the asteria-game container; the cluster
infrastructure (sidecar / convergence / chain-sync-client) must
hold under fault regardless of what asteria does. Whatever
asteria introduces — utxo-indexer load on relay1, spawn tx
churn — has to be the thing fixed, not the cluster's
invariants.

Also strips the runtime-mount workarounds added to the sidecar
block (the ./no-op-finally.sh bind-mount and the
chain-sync-client tmpfs override). They were inert anyway —
Antithesis's composer discovers driver scripts at image-bake
time, not container-runtime — so leaving them only created
cargo-cult clutter.

Compose tag bumped to c99e992 (BootstrapMain top-level catch),
which is the only legitimate fix from the previous attempt.

This reopens the question raised by run 2: are
convergence/finally_tips_agree.sh and chain-sync-client/
parallel_driver_flaky_chain_sync.sh failing because relay1 is
falling behind p1/p2/p3 under load from the asteria-game
container's utxo-indexer ChainSync? If so, the fix is in
asteria-game (don't stress relay1), not in dropping the
checks.

Signed-off-by: aarish mansur <[email protected]>

From https://github.com/IntersectMBO/plutus at ac40fae4dea9dcad51b38a9c5c48148655cb13a2

From https://github.com/IntersectMBO/plutus at ac40fae4dea9dcad51b38a9c5c48148655cb13a2

From https://github.com/IntersectMBO/plutus at ac40fae4dea9dcad51b38a9c5c48148655cb13a2

From https://github.com/IntersectMBO/plutus at ac40fae4dea9dcad51b38a9c5c48148655cb13a2

From https://github.com/IntersectMBO/plutus at ac40fae4dea9dcad51b38a9c5c48148655cb13a2