Cardano Updates

Signed-off-by: Francisco Javier Ribo Labrador <[email protected]>

Signed-off-by: Francisco Javier Ribo Labrador <[email protected]>

Adds a minimal test that compiles unsafeFromBuiltinData on a 3-constructor
type in the default SumsOfProducts mode (no BuiltinCasing pragma).
This captures the caseInteger fallback regression for comparison.

added:
* github:input-output-hk/mithril/2bbef5a24cfb113a21c55d2d04d7a30b6046ba03#mithril-client-cli
* github:input-output-hk/mithril/2bbef5a24cfb113a21c55d2d04d7a30b6046ba03#mithril-signer
removed:
* github:input-output-hk/mithril/7127c11c6113d39222ae659c8e366da058c513a0#mithril-client-cli
* github:input-output-hk/mithril/7127c11c6113d39222ae659c8e366da058c513a0#mithril-signer

Signed-off-by: Sasha Bogicevic <[email protected]>

Signed-off-by: Sasha Bogicevic <[email protected]>

# Description

Forkers have been a source of headaches for a very long time already,
and all due to the limitation of the Resource registry that enforces
registries to only be used from known threads. This has lead to a
situation where we had hierarchies of registries just to satisfy that
rule and even we had to extend the resource-registry API to allow
transferring between registries which is unsafe.

The general pattern followed now is:
1. At the ledgerdb level we only keep track of the resources, running
WithTempRegistry while opening the DB and then closing them when closing
the LedgerDB.
2. Forkers that open new handles are open in a `with*` combinator style,
so the handles are deallocated when exiting the scope (or committed).
3. Forkers that only duplicate existing handles (read-only forkers) are
only used in Mempool and LocalStateQuery and there we put them in a
registry, in particular in the top level registry.
4. The handles are not tracked directly---each handle is tracked
indirectly because some forker or the LedgerDB owns it and is tracked.
Forkers are tracked so that they can be released promptly which avoids
space-leaks and permits the backends (LSM/LMDB) to do their gradual
bookkeeping/rearranging work.
5. In particular, when the node is shutting down, there is no need to
close each handle/forker:
   1. in InMemory it doesn't matter as it is pure
2. in LSM, closing the session will close any open handles, and closing
the session happen when shutting down the node,
3. in LMDB, each forker has one single read-transaction open and it will
be closed as described above. There are no further resources allocated
on each step. Also closing the backing store is optional as described in
the LMDB docs (also mentioned in LedgerDB API).

Sadly, the change is so fundamental that there is no meaningful way of
splitting the changes into reviewable commits that compile on their own.

Proposed review order (recommended to disable whitespace-diff in Github
diff view and hide already viewed files):

1. Ouroboros.Consensus.Storage.ChainDB.API
5. Ouroboros.Consensus.MiniProtocol.LocalStateQuery.Server +
Ouroboros.Consensus.Network.NodeToClient
7. Ouroboros.Consensus.Mempool.{Impl.Common, Update, Init}
8. Ouroboros.Consensus.Storage.ChainDB.ChainSel
9. Ouroboros.Consensus.Storage.ChainDB.Impl.Types +
Ouroboros.Consensus.Storage.ChainDB.Impl.Query
10. Ouroboros.Consensus.Storage.ChainDB.Impl
11. Ouroboros.Consensus.Storage.ImmutableDB.{Impl, Impl.Validation}
12. Ouroboros.Consensus.Storage.VolatileDB.Impl
13. Ouroboros.Consensus.Storage.LedgerDB.API (both the API changes and
the initialization)
14. Ouroboros.Consensus.Storage.LedgerDB
15. Ouroboros.Consensus.Storage.LedgerDB.Forker
16. Ouroboros.Consensus.Node (just comments changes)
17. Ouroboros.Consensus.NodeKernel
18. Ouroboros.Consensus.Storage.LedgerDB.V2.LedgerSeq
19. Ouroboros.Consensus.Storage.LedgerDB.V2.Forker
20. Ouroboros.Consensus.Storage.LedgerDB.V2.Backend
21. Ouroboros.Consensus.Storage.LedgerDB.V2.InMemory
22. Ouroboros.Consensus.Storage.LedgerDB.V2.LSM
23. Ouroboros.Consensus.Storage.LedgerDB.V2    
24. Ouroboros.Consensus.Storage.LedgerDB.V1.Forker
25. Ouroboros.Consensus.Storage.LedgerDB.V1.Snapshots
26. Ouroboros.Consensus.Storage.LedgerDB.V1

The rest of the changes are just adapting tests or adapting the
cardano-tools to use the new access pattern. I did not do any meaningful
change in the tests by my will, I only followed GHC errors where they
took me.

This is just for maven and iOSX64 was giving an expected error, so deactivated.

* Add ./script/nix-format.sh for non-Nix users.
* Add nixfmt in our Nix pre-commit hook.
* Add Github CI check

State machine (StIdle/StBusy/StDone), CBOR codec, client helpers
(request_next, done), and security audit. Protocol ID 18. All Leios
types are opaque blobs. 19 new tests including allocation bounds,
codec round-trips, and MemBearer integration. 191 total tests pass.

Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>

Switch mux from RoundRobin to StrictPriority scheduler so Praos
protocols always outprioritize Leios, preventing head-of-line blocking.
Add named priority constants, fix KeepAlive/PeerSharing/Leios priority
assignments, consolidate deferred items into Future Work section.

Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>