[stable2503] Backport #8373

[paritytech-release-backport-bot]

Backport #8373 into stable2503 from lexnv.

See the documentation on how to use this bot.

[paritytech-release-backport-bot]

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin backport-8373-to-stable2503
git worktree add --checkout .worktree/backport-8373-to-stable2503 backport-8373-to-stable2503
cd .worktree/backport-8373-to-stable2503
git reset --hard HEAD^
git cherry-pick -x 9869517b4dc851469e6d854a263f82ff32133524
git push --force-with-lease

[github-actions]

This pull request is amending an existing release. Please proceed with extreme caution,
as to not impact downstream teams that rely on the stability of it. Some things to consider:

• Backports are only for 'patch' or 'minor' changes. No 'major' or other breaking change.
• Should be a legit fix for some bug, not adding tons of new features.
• Must either be already audited or not need an audit.

Emergency Bypass

If you really need to bypass this check: add validate: false to each crate
in the Prdoc where a breaking change is introduced. This will release a new major
version of that crate and all its reverse dependencies and basically break the release.

[lexnv]

Tested the PR in versi-net (based on origin/master):

• networking: Update litep2p network backend to v0.9.4 #8373
• errors: https://grafana.teleport.parity.io/goto/1yLDANbHg?orgId=1 (expected)
• warnings: https://grafana.teleport.parity.io/goto/9wVO0NbNR?orgId=1 (expected)
• overview dashboards: https://grafana.teleport.parity.io/goto/L4yd0NxNg?orgId=1 (no abnormal behavior)

Synced a full node in Kusama directly from this branch, no warnings / errors encountered. The node is operating normally.