Cardano Updates

Pulls in the depth checklist (cluster_fork_depth_N_observed) and
adversary_observed_as_peer Sometimes assertions onto the
cardano_node_adversary testnet.

Two new probes on top of the existing fork-tree state machine.

Layer 3 — depth checklist
  - Tracks maxForkDepth in tracer-sidecar State.
  - Emits one Sometimes assertion per depth threshold from 2 up to
    k - 1: cluster_fork_depth_2_observed, _3_observed, ... _k-1.
  - Reading the report, the highest passed threshold tells you how
    deep the cluster forked under fault injection without drilling
    into per-event details.

Layer 2 — peer-observability probe
  - Adds adversary_observed_as_peer Sometimes assertion.
  - Fires on the first Net.InboundGovernor.* log line whose JSON
    contains the substring "adversary.example", proving the
    adversary's chain-sync sessions reached a producer's peer-
    selection layer at least once during the run (not just the
    kernel TCP backlog).
  - Uses a substring check against the encoded JSON, so we don't
    pin the message schema — the producer's tracer can rename
    fields without breaking the probe.

State now carries maxForkDepth and adversaryObservedAsPeer; both
land alongside the existing forkObserved / forkExceededK flags
inside updateForkTree's refresh function and a new generic
mkSpec rule.

feat: add EDR on switching to our own mini-protocol implementations

Signed-off-by: Jenita <[email protected]>
Co-authored-by: Jenita <[email protected]>

Signed-off-by: Chris Gianelloni <[email protected]>

Signed-off-by: Chris Gianelloni <[email protected]>

Note: this test is currently failing has nothing in the code exist to
handle this case yet.

Allowing to define a "catch all" variant for deserialization