Cardano Updates

Validate ledger value arithmetic with checked conversions so invalid lovelace
overflow and negative mint/burn results return validation errors instead of
wrapping into large u64 values.

Related: #783
Tested: RUSTC_WRAPPER= cargo test -p pallas-validate
Tested: cargo-fuzz fixed seeds for value_arithmetic_invariants and minted_value_invariants

Add new Plutus scripts (V1-V3) and Imp tests that verify TxInfo
translation by passing expected values via the redeemer and validating
them on-chain.

This depends on new package cardano-crypto-leios from cardano-base

This avoids redundant import warnings on newer GHC versions

Add a test suite that decodes every example configuration through the autodocodec-derived parsers and the full configuration-file pipeline, guarding against drift between the parsers and the example configs.

Add a small executable that prints the configuration JSON Schema (the whole single-file configuration, or a single named component), with --list and --help.

Add Cardano.Configuration.Schema, which derives a JSON Schema for each configuration component, and a merged whole-config schema, directly from the autodocodec codecs, so the schema cannot drift from the parser. The schemas target draft-07 and surface the codecs' annotations as descriptions.

Replace the hand-written FromJSON instances with autodocodec HasCodec codecs (deriving FromJSON/ToJSON via Autodocodec), so the parsers and the configuration documentation share a single definition. The LedgerDB snapshot configuration moves to the predictable-snapshots model: a Snapshots policy that is either a named policy or an explicit options object, with the example configs updated to match.

Adopt the predictable-snapshots LedgerDB model from the upcoming node (f-f/prepare-11.1, predictable-snapshots): the LedgerDB Snapshots key is either a named policy (e.g. "Mithril") or an explicit options object (SnapshotInterval, SlotOffset, RateLimit, MinDelay, MaxDelay, NumOfDiskSnapshots), replacing the flat snapshot fields. The example configs are updated to match.

The parsers remain hand-written FromJSON, for consumers who want the plain-JSON configuration without autodocodec.

Add a test suite that decodes every example configuration through the autodocodec-derived parsers and the full configuration-file pipeline, guarding against drift between the parsers and the example configs.