[stable2503] Backport #7670

[paritytech-cmd-bot-polkadot-sdk]

Backport #7670 into stable2503 from davxy.

See the documentation on how to use this bot.

[paritytech-cmd-bot-polkadot-sdk]

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

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

[ggwpez]

We are pulling in a lot of sp- dependencies multiple times, since the bandersnatch stuff is not on crates-io...

[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.

[EgorPopelyaev]

@ggwpez do we need to bump pallet-sassafras and sp-core here? aka prdoc stuff😄

[ggwpez]

Yea true - dont know why the original was marked as silent 🫠

[EgorPopelyaev]

@davxy @ggwpez it looks like there is a conflict in the Cargo.lock appears now, guys, could you please have a look?