Cardano Updates

This CPS documents the problem of uncoordinated handle namespaces on
Cardano and proposes requirements for a governance solution.

Submitted following the discussion in CIP PR #1187 where the CIP
editors identified the need for a broader problem statement before
a technical solution can be proposed.

Related: https://github.com/cardano-foundation/CIPs/pull/1187

From https://github.com/IntersectMBO/cardano-base at d6e5c68bbb87f528fc1926a32c462c5bf06f1782

From https://github.com/IntersectMBO/cardano-base at d6e5c68bbb87f528fc1926a32c462c5bf06f1782

Add re-exports for ApplyTxError(..), ConwayLedgerPredFailure(..),
ConwayUtxowPredFailure(..), ConwayUtxoPredFailure(..), Mismatch(..),
and hashToTextAsHex so downstream consumers (cardano-cli) can
pattern-match on ledger predicate failures for human-readable
error rendering.

Runs both applyTx (phase 1) and evaluateTransactionExecutionUnits (phase 2)
independently in a single LocalStateQueryExpr session, returning both results
via TxValidationResult.

The contingency registry_script.hash was 27.5 bytes (missing a
trailing 8). The on-chain hash is the correct 28-byte value;
intent.json builders comparing the two abort with AnchorMismatch
"registry_script.hash" (Just Contingency), blocking every
contingency-flavoured operation on a fresh clone.

Adds a new local state query that runs applyTx against the current
ledger state and returns the raw result. The provisional implementation
queries the full EpochState and runs applyTx client-side; this will be
replaced by a dedicated node-side consensus query.

Exposed from Cardano.Api.Query alongside other queries.

Add re-exports for ApplyTxError(..), ConwayLedgerPredFailure(..),
ConwayUtxowPredFailure(..), ConwayUtxoPredFailure(..), Mismatch(..),
and hashToTextAsHex so downstream consumers (cardano-cli) can
pattern-match on ledger predicate failures for human-readable
error rendering.

Runs both applyTx (phase 1) and evaluateTransactionExecutionUnits (phase 2)
independently in a single LocalStateQueryExpr session, returning both results
via TxValidationResult.