Bump block numbers, update/remove unstable/stale snapshots

[rockbmb]

This PR does the following

• update known-good block numbers for Polkadot to fix coretimePolkadot.multisig.proxy E2E test failure.
• update People E2E tests' snapshots
• change accounts used in Encointer <-> KAH XCM test to testAccounts, as the defaultAccountsSr25519 accounts it was using had their balances change sometimes
• disable PAH <-> Polkadot <-> Collectives runtime upgrade XCM test because of failures in XCM processing
• update PAH staking tests/snapshots to reflect what was done for Kusama in Refactor accounts snapshots #562

Root Cause for 1.

The 2-of-3 multisig as standard proxy with announcement and delay test was failing exclusively on Coretime Polkadot (Kusama passed with identical code and parameters). The test loops through 4 iterations of multisig create/approve cycles (proxy delay of 7 local blocks), producing ~11 newBlock() calls.

At the previous known-good block number (CORETIMEPOLKADOT_BLOCK_NUMBER=3874737), Bob's final asMulti approval on the 4th iteration was rejected during block building. system.dryRun on the signed extrinsic confirmed the cause:

Iteration 1 dryRun: {"Ok":{"Ok":[]}}
Iteration 2 dryRun: {"Ok":{"Ok":[]}}
Iteration 3 dryRun: {"Ok":{"Ok":[]}}
Iteration 4 dryRun: {"Err":{"Invalid":"ExhaustsResources"}}

The extrinsic was structurally identical across all iterations — same call, same maxWeight, same accounts. The block at iteration 4 simply could not fit it, while iterations 1–3 could. Kusama Coretime at its known-good block number did not exhibit this.

Fix

Update known-good block numbers. The new Coretime Polkadot block does not reproduce the ExhaustsResources rejection.

[github-actions]

No issues found.