[stable2506] Backport #10180

[paritytech-release-backport-bot]

Backport #10180 into stable2506 from bkchr.

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-10180-to-stable2506
git worktree add --checkout .worktree/backport-10180-to-stable2506 backport-10180-to-stable2506
cd .worktree/backport-10180-to-stable2506
git reset --hard HEAD^
git cherry-pick -x 12f9d5987303545220466c62fa5e0621abc72025
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.

[EgorPopelyaev]

@bkchr and here there are some failing tests🙏: https://github.com/paritytech/polkadot-sdk/actions/runs/19143505440/job/54715219473?pr=10228

[paritytech-workflow-stopper]

All GitHub workflows were cancelled due to failure one of the required jobs.
Failed workflow url: https://github.com/paritytech/polkadot-sdk/actions/runs/19162694110
Failed job name: fmt

[EgorPopelyaev]

@bkchr Basti, do these crates mentioned in the semvercheck need to be bumped as well:

• frame-executive
• cumulus-pallet-parachain-system
• polkadot-runtime-parachains
• pallet-babe
• pallet-revive
• pallet-aura

(sc-tracing can be ignored, it had only formatting issue in the Cargo.toml)

[bkchr]

• cumulus-pallet-parachain-system

• pallet-babe

• pallet-aura

There are only test changes and they can be ignored.