Cardano Updates

From https://github.com/IntersectMBO/cardano-node at 1e6d8228693ab2aa4e1d7305e7bdcc57cdd278e4

From https://github.com/IntersectMBO/cardano-node at 1e6d8228693ab2aa4e1d7305e7bdcc57cdd278e4

From https://github.com/IntersectMBO/cardano-node at 1e6d8228693ab2aa4e1d7305e7bdcc57cdd278e4

bumps cardano-testnet and cardano-tracer minor versions

The node is allowed to crash only at startup, before consensus and
diffusion layers have been launched, if an invalid ledger peer
snapshot file is specified.

Support ghc-9.14

Replace parameterized ScriptRequirements GADT with flat unparameterized ADTs

Refactor such that each example from an era is build on top of the
example of the previous era.

Allows:
* reduced duplication
* each example of each era has most fields set with values

ScheduledMerges: allow empty levels

chore(main): release cardano-connect-with-wallet-core 0.2.10

The new `ConformanceTest` record contains fields for all data formerly used
to run a test via `forAllGenesisTest` helper, plus other fields that pertain
to its evaluation as a test property on a`TestTree`.
A value of this type is defined for each point-schedule/genesis test.

All such `ConformanceTest`s are arranged in a `TestSuite`s, a data
structure introduced with the goal of eventually exporting them as
part of a new sublibrary for the Conformance Testing of Consensus harness
(see https://github.com/tweag/cardano-conformance-testing-of-consensus).
This data structure is designed to optimize single test lookups,
while retaining the necessary structure to be compiled back to a `TestTree`,
so that the introduced changes preserve the semantics of the
`ouroboros-consensus-diffusion:test:consensus-test` test suite.

To accomplish this, a new data type is introduced in each module as a `key`
for the locally defined `TestSuite`, such that each test in the module
corresponds to a unique value (nullary constructor) of this type. This means
that including a new test in a `TestSuite` requires the extension of such key
type by e.g. introducing a new data constructor. These `key` types are aggregated
into higher level key types to reify the nested grouping of the original
tasty `TestTree`s. It is by combining `mkTestSuite` and `group` that a higher
level `TestSuite` can be defined. The `SmallKey key` constraint is needed for
their exhaustive construction, via `newTestSuite` and `mkTestSuite`; as
implemented, a `TestSuite` is a total map.

Co-authored-by: Sandy Maguire <[email protected]>

`NoThunks` instances are used for memory leak detection during development,
but predicate failures should never be retained in the ledger state - they
are only used for validation results. Removing these instances reduces
code maintenance burden and instance derivation overhead.

This change removes `NoThunks` instances from:

- All predicate failure types across Shelley, Allegra, Alonzo, Babbage,
  Conway, and Dijkstra eras
- All `ContextError` types (`AlonzoContextError`, `BabbageContextError`,
  `ConwayContextError`, `DijkstraContextError`)
- The `NoThunks (ContextError era)` constraint from the `EraPlutusContext` class
- The `NoThunks` deriving instance for `CollectError`