[stable2512] Backport #11168

[paritytech-release-backport-bot]

Backport #11168 into stable2512 from sigurpol.

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-11168-to-stable2512
git worktree add --checkout .worktree/backport-11168-to-stable2512 backport-11168-to-stable2512
cd .worktree/backport-11168-to-stable2512
git reset --hard HEAD^
git cherry-pick -x 79bc8a968a2eda1ae127740ee1a20ff10e375950
git push --force-with-lease

[sigurpol]

@EgorPopelyaev , I've marked the change for staking-async as major because we are adding a Config item for the pallet at runtime (MinSetKeysBond) which is mandatory to specify. At the end of the day, its is not something the user will face it, just AssetHub chains will have to set it and I will do in the corresponding runtime PR

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

[sigurpol]

@EgorPopelyaev , I've marked the change for staking-async as major because we are adding a Config item for the pallet at runtime (MinSetKeysBond) which is mandatory to specify. At the end of the day, its is not something the user will face it, just AssetHub chains will have to set it and I will do in the corresponding runtime PR

ok as discussed - minor + validated false.