benchmarking: fix DB read/write counts

[sigurpol]

PR #10802 added reset_read_write_count() at the end of commit_db() to prevent warmup operations from appearing in benchmarking results. However, commit_db is called twice: one on on_before_start() closure before benchmark, and one after benchmark execution after benchmark.
This PR whitelists the warmup key used in commit_db so that it doesn't appear in the read/write count.

We also regenerated staking-async weights (wrongly benchmarked in #10802) and conviction-voting to check both v1 and v2 benchmarking.

Driven-by: update try-runtime-cli to v0.10.1 as an attempt to fix the issue for which CI regularly fails in the check-migration (WAH) job in ./try-runtime create-snapshot --uri wss://westend-asset-hub-rpc.polkadot.io:443 snapshot.raw`

[sigurpol]

/cmd prdoc --audience runtime_dev --bump patch

[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/21518053752
Failed job name: check-runtime-compatibility

[sigurpol]

Tested via target/release/frame-omni-bencher v1 benchmark pallet --runtime ./target/release/wbuild/asset-hub-westend-runtime/asset_hub_westend_runtime.compact.compressed.wasm --pallet pallet_staking_async --extrinsic "force_apply_min_commission" --steps 2 --repeat 1:

Pallet: "pallet_staking_async", Extrinsic: "force_apply_min_commission", Lowest values: [], Highest values: [], Steps: 2, Repeat: 1
Raw Storage Info
========
Storage: `Staking::MinCommission` (r:1 w:0)
Proof: `Staking::MinCommission` (`max_values`: Some(1), `max_size`: Some(4), added: 499, mode: `MaxEncodedLen`)
Storage: `Staking::Validators` (r:1 w:1)
Proof: `Staking::Validators` (`max_values`: None, `max_size`: Some(45), added: 2520, mode: `MaxEncodedLen`)

Median Slopes Analysis
========
-- Extrinsic Time --

Model:
Time ~=    58.33
              µs

Reads = 2
Writes = 1
Recorded proof Size = 640

Min Squares Analysis
========
-- Extrinsic Time --

Model:
Time ~=    58.33
              µs

Reads = 2
Writes = 1
Recorded proof Size = 640

Seems we are back on track @mertwole , @ggwpez

[mertwole]

Aldo the pallet-staking-async weights need to be benched again as #10802 removed DB read/write weights there

[sigurpol]

Aldo the pallet-staking-async weights need to be benched again as #10802 removed DB read/write weights there

Fair - I was not sure if doing it in a follow-up PR or here, but seems reasonable to do it here. Lemme

[sigurpol]

/cmd bench --pallet pallet_staking_async --runtime asset-hub-westend

[github-actions]

Command "bench --pallet pallet_staking_async --runtime asset-hub-westend" has started 🚀 See logs here

[ggwpez]

/cmd bench --pallet pallet_conviction_voting --runtime asset-hub-westend
(to also check V1)

[github-actions]

Command "bench --pallet pallet_conviction_voting --runtime asset-hub-westend" has started 🚀 See logs here

[sigurpol]

/cmd bench --pallet pallet_conviction_voting --runtime asset-hub-westend (to also check V1)

let me add that to the prdoc too 😄

[paritytech-release-backport-bot]

Created backport PR for stable2512:

• [stable2512] Backport #10947 #10975 with remaining conflicts!

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

git fetch origin backport-10947-to-stable2512
git worktree add --checkout .worktree/backport-10947-to-stable2512 backport-10947-to-stable2512
cd .worktree/backport-10947-to-stable2512
git reset --hard HEAD^
git cherry-pick -x a78b18a5cc547141bfd5c10eb17593239e1e2509
git push --force-with-lease