Release `2418` distribution

[jpraynaud]

Why

In order to deploy new features, improvements and bug fixes, we need to release a new distribution.

What

Create and release a new distribution 2418

How

Important

• Breaking change on Mithril client certificate hash
• Rollout of new Cardano node 8.10?
• Upgrade tokio 1.37+

Phase 1: Prepare distribution

• Update repository dependencies (tokio to 1.37.0)
• Check that all minor versions of all crates have been bumped for breaking change (if needed)
• Check if versions of repository linked crates are correct for publication to crates.io(mithril-common, mithril-client)
• Check if Cardano minimum supported versions in networks.json must be updated following the runbook

Phase 2: Rollout pre-release distribution

• Tag and deploy a 2418.1-pre pre-release distribution on the pre-release-preview network
• Manual recomputation of certificate hashes of pre-release-preview with runbook
• Fill 'Highlights' and release notes section in the pre-release page on GitHub
• Make sure pre-release-preview is working as expected
• Make sure libraries version next have been published on npm registry
• Run an all green client multi-platform test in the CI
• Prepare a draft PR for rotating the documentation
• Announce the pre-release on discord channel
• Announce any breaking change in #cardano-scaling slack channel for pre-release
• Wait for at least 3 signers running the new version (could be more if era change is tested) over at least 2 epochs

Phase 3: Rollout release distribution

• Tag and deploy a 2418.1 release distribution on the pre-release-preview network
• Fill highlights and release notes section in the release page on GitHub
• Make sure pre-release-preview is working as expected
• Update networks compatibility table in release notes
• Release the 2418.1 distribution
• Manual recomputation of certificate hashes of release-mainnet with runbook
• Manual recomputation of certificate hashes of release-preprod with runbook
• Make sure release-mainnet is working as expected
• Make sure release-preprod is working as expected
• Make sure libraries have been published on crates.io
• Make sure libraries version latest have been published on npm registry
• Merge the PR for rotating the documentation
• Review and rotate CHANGELOG.md
• Announce the release on discord channel (with breaking-change)
• Announce any breaking/new feature change in:
  • #cardano-scaling slack channel for release
  • Dev blog post:
    • TBD