Cardano Updates

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

added:
* github:input-output-hk/mithril/6f51b1261472feb1b92a564863a6968f6149f38d#mithril-client-cli
* github:input-output-hk/mithril/6f51b1261472feb1b92a564863a6968f6149f38d#mithril-signer
removed:
* github:input-output-hk/mithril/aab34211273e57a3da79a394cc2c604e8f277bc4#mithril-client-cli
* github:input-output-hk/mithril/aab34211273e57a3da79a394cc2c604e8f277bc4#mithril-signer

chunk_for_slot hardcoded 21600 slots per chunk, which only holds for
mainnet and preprod (k = 2160). Preview chunks span 4320 slots (k = 432),
so create-snapshots compared incompatible chunk numbers, wrongly concluded
the local cardano-db covered the target slots and skipped the Mithril
download, then failed to store the ledger snapshot.

- Pin contra-tracer to Russoul/contra-tracer@5ad4ac8 which adds
  INLINE contramap and strict second argument / result, on top of
  the existing INLINE runTracerA and strict (***) fixes.

- Revert the heap limit from 1500M back to 900M and instead set
  TASTY_NUM_THREADS=1 on all platforms. The OOM is caused by Tasty
  running all tests concurrently (one thread per CPU via
  setNumCapabilities), stacking their peak residencies. Each
  individual test fits well within 900 MB; the fix is sequential
  execution, not a larger limit.

Periodically recompute the live-peer set for each staged entry from
current ChainSync candidate fragments; when no live peer's candidate
contains the staged CertRB, the EB closure is unreachable and the
entry is evicted. Eviction wakes the parked BlockFetch client thread
via a per-call StrictTMVar with StagedEvicted so it can surface a
FailedToAddBlock verdict instead of leaking the thread (PR #2058
open point 4). Drain switches to the same TMVar mechanism, signalling
StagedReleased on closure arrival.

The CertRB staging gate consulted both getCurrentChain and the
ChainSync candidate fragments to locate the parent header's
headerLeiosAnnouncement. A BlockFetch-delivered block is by
construction fulfilling some candidate, so the parent must live in
one of the live candidate fragments; the locally selected chain is
incidental. Dropping it keeps the gate's decision aligned with the
candidate it's serving (issue #890 follow-up bullet 1).

Signed-off-by: Akhil Repala <[email protected]>

* [js] mithril-explorer from `0.8.2` to `0.8.3`

Provide generator for conway-based UTxO with valid domain values.