Cardano Updates

Co-authored-by: sg-doc-holiday[bot] <219201796+sg-doc-holiday[bot]@users.noreply.github.com>

feat: use peerjs instead of meerkat for cip45

Signed-off-by: Doc Holiday <[email protected]>

Signed-off-by: Doc Holiday <[email protected]>

Signed-off-by: Doc Holiday <[email protected]>

Signed-off-by: Doc Holiday <[email protected]>

Signed-off-by: Doc Holiday <[email protected]>

Signed-off-by: Doc Holiday <[email protected]>

Adapt cardano-cli to the cardano-api removal of ProtocolParametersUpdate
in favour of EraBasedProtocolParametersUpdate era.

- Read.hs: bring IsShelleyBasedEra era into scope via
  shelleyToBabbageEraConstraints, satisfying the HasTextEnvelope instance
  for the now era-indexed UpdateProposal era without changing the
  function's exposed type.

- Friendly.hs: rewrite friendlyProtocolParametersUpdate to take a
  ledger PParamsUpdate directly (caller in friendlyUpdateProposal does
  the createEraBasedProtocolParamUpdate conversion) and dispatch on
  ShelleyBasedEra constructors to determine which fields apply per era.
  Helper functions per field group carry their own ledger constraints
  (EraPParams, ProtVerAtMost N, AlonzoEraPParams, BabbageEraPParams)
  and the case branches resolve them via instance lookup once the era
  is concrete - no eon witnesses required.

  Output preserves the prior JSON shape exactly (verified by
  hprop_golden_view_alonzo_update_proposal_yaml). Cost models and
  Conway-only governance fields are deliberately not emitted, matching
  prior behaviour.

- Compatible/Governance/Run.hs: drop the redundant
  createEraBasedProtocolParamUpdate / fromLedgerPParamsUpdate round-trip
  in shelleyToBabbageProtocolParametersUpdate; makeShelleyUpdateProposal
  now takes EraBasedProtocolParametersUpdate era directly.

- cardano-cli.cabal: add cardano-ledger-binary dep for getVersion
  (used to render the protocol-version major component).

This mirrors the BlockForging machinery where blk-specifics would be
part of the handle instead of a type class.

Pins the rendered YAML shape of an alonzo-era transaction whose update
proposal exercises every field that friendlyProtocolParametersUpdate is
expected to render. This locks down the flat-key output (preserving keys
like "max block body size", "execution prices", "min UTxO value", "min
pool cost", etc.) so any subsequent rewrite of the renderer cannot
silently change the JSON shape.

The proposal is built via `compatible alonzo governance action
create-protocol-parameters-update`, embedded into a tx via `compatible
alonzo transaction signed-transaction --update-proposal-file`, and
viewed via `debug transaction view --output-yaml`.

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

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