Design strategy for enhanced support of Cardano versions

## Why
Currently more than 25% of Cardano nodes are running on `10.1.4` (see https://pooltool.io/networkhealth) which is not officially supported by Mithril. We want to provide support for a broader range of Cardano node versions and follow the hard fork activation.

## What
Design strategy to support more Cardano node versions in Mithril.

## How

- [ ] Have a clear guidelines on which versions are supported (released or not, how many users running it, after/before hardfork)
- [x] Evaluate the gap to test all of the supported versions (e2e, backward compatibility, multi-platform client test, ...)
- [x] Propose evolutions in the documentation (network matrix and `networks.json` file)
- [x] What about node diversity and compatibility (in particular prepare `networks.json` structure evolution)
- [ ] Design qualification strategy for new version of Cardano node (GitHub Actions jobs for automating https://github.com/input-output-hk/mithril/issues/2790, ...)
- [ ] Cardano node update only distributions for Mithril for better reactivity (process like hotfix to avoid working on `main` branch)
- [ ] Redact ADR?
- [ ] TBD