Cardano Updates

Flake lock file updates:

• Updated input 'CHaP':
    'github:intersectmbo/cardano-haskell-packages/25591f43ab943d5a070db5e8a2b9ff3a499d4d92?narHash=sha256-ijnHTQ6eKIQ9FpEqDKt6c7vuFYN8aOBDhonp67utx2s%3D' (2024-10-30)
  → 'github:intersectmbo/cardano-haskell-packages/94b36615fa8f5aaae885627273bc8499eeebdca5?narHash=sha256-zDJVC0/vTaZq%2Bqs2nYlSCKh19PB0K0eAtJZvn4hRHAI%3D' (2024-12-19)
• Updated input 'hackageNix':
    'github:input-output-hk/hackage.nix/6dc43e5e01f113ce151056a8f94bce7bb2f13eb9?narHash=sha256-sIglYcw8Dacj4n0bRlUWo%2BNLkDMcVi6vtmKvUyG%2BZrQ%3D' (2024-10-16)
  → 'github:input-output-hk/hackage.nix/0cd0b766d42b653a937709d7b505cc92929e4d8f?narHash=sha256-2t1ZDzsqOOjn/XX41rmRI1YPQLa7bACPTVlkRjoAThE%3D' (2024-12-21)

Co-authored-by: Marcin Szamotulski <[email protected]>

"diffusionMode" can be either `"InitiatorOnly"` or
`"InitiatorAndResponder"`.  If not given, the latter is the default
- for backward compatibility.  When "InitiatorOnly" is used, the
connections to these local roots will only negotiate `InitiatorOnly`
mode (it won't be possible to be reused by the other side) and will not
bind to the server address, e.g. it will be made from an ephemeral port.
See https://github.com/IntersectMBO/ouroboros-network/issues/5020 why
this feature was requested by some SPOs.

An example configuration:
```json
{ "localRoots":
    [ { "accessPoints":
          [ { "address": "10.0.0.1"
            , "port": 3001
            }
          ]
      , "advertise": false
      , "diffusionMode": "InitiatorOnly"
      , "warmValency": 1
      , "hotValency": 1
      }
    , { "accessPoints":
          [ { "address": "10.0.0.2"
            , "port": 3001
            }
          ]
      , "advertise": true
      , "diffusionMode": "InititiatorAndResponder"
      , "warmValency": 1
      , "hotValency": 1
      }
    ]
, "publicRoots": []
, "useLedgerAfterSlot": -1
}
```

This change introduces support for big ledger peers in the node.
A new optional entry in network topology JSON parser is added that is intended
to point to a path containing a serialized snapshot of big ledger peers
taken from some slot a priori. When present, this file is decoded
at node startup, or when a SIGHUP is triggered, and made available
to the diffusion layer via reading from a TVar.