Cardano Updates

This class based approach mirrors other components of the consensus code
base where abstract code is made block-specific via type classes.

[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

Generated by cargo-workspaces

Backports the handshake half of #747 to the 0.18.x line so downstream
consumers can negotiate NodeToClient sessions with cardano-node 10.x
peers, including the 10.7.x release that targets the van Rossem hard
fork (protocol version 11).

The remaining changes from #747 (queries_v16 additions, the new
ConwayLedgerFailure tags, and the pallas-network2 / pallas-hardano
counterparts) depend on modules introduced after this branch diverged
and are intentionally out of scope.

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
  EraBasedProtocolParametersUpdate era and dispatch on the GADT, with one
  helper per sub-record (common, deprecated-after-mary,
  deprecated-after-babbage, shelley-to-alonzo, alonzo-onwards,
  introduced-in-babbage). JSON output remains flat with the original key
  names preserved. Cost models and Conway-only governance fields are
  deliberately not emitted, matching prior output; surfacing them under
  new keys can be done as a follow-up.

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

Backports the handshake half of #747 to the 0.18.x line so downstream
consumers can negotiate NodeToClient sessions with cardano-node 10.x
peers, including the 10.7.x release that targets the van Rossem hard
fork (protocol version 11).

The remaining changes from #747 (queries_v16 additions, the new
ConwayLedgerFailure tags, and the pallas-network2 / pallas-hardano
counterparts) depend on modules introduced after this branch diverged
and are intentionally out of scope.

Signed-off-by: Dev10-sys <[email protected]>

Update haskell-language-server-2.14.0.0

`goldenExampleEraTxCborSpec` allows us to generate a `Spec` for
generating a `golden/tx.cbor` golden file out of some `Tx` provided as a
parameter.

Then, for each era's test-suite, we call this function to generate the
golden file using the example transaction we have defined for each era.

We also extended `EraTest` so that we don't need to manually call
`getDataFileName` in order to get the fullpath for each era's cabal
project.

We also create new `Binary.Golden` modules for Mary and Babbage (previously
they reused Allegra's and Alonzo's respectively, which used the wrong era's
example transactions).

Additionally, fix `exampleDijkstraBasedTopTx` to not add PlutusV4 scripts
to `scriptTxWitsL`: PlutusV4 is not included in Dijkstra's
`transaction_witness_set` CDDL, so those scripts were
silently dropped during serialization, causing a roundtrip failure.

Upgrade pumba flake so it builds on modern mac hardware.

`goldenExampleEraTxCborSpec` allows us to generate a `Spec` for
generating a `golden/tx.cbor` golden file out of some `Tx` provided as a
parameter.

Then, for each era's test-suite, we call this function to generate the
golden file using the example transaction we have defined for each era.

We also extended `EraTest` so that we don't need to manually call
`getDataFileName` in order to get the fullpath for each era's cabal
project.

We also create new `Binary.Golden` modules for Mary and Babbage (previously
they reused Allegra's and Alonzo's respectively, which used the wrong era's
example transactions).

Additionally, fix `exampleDijkstraBasedTopTx` to not add PlutusV4 scripts
to `scriptTxWitsL`: PlutusV4 is not included in Dijkstra's
`transaction_witness_set` CDDL, so those scripts were
silently dropped during serialization, causing a roundtrip failure.