SERVER-131665 added filtering of expired historical chunk documents during authoritative collection metadata recovery. A long-running query freezes its ownership view in a refcounted CollectionMetadataTracker captured at the start. Installing newly recovered (filtered) metadata must leave that tracker untouched. This ticket adds the regression guard for this case.

The existing integration test (jstests/noPassthrough/shard_catalog/shard_catalog_expired_history_filtering.js) forces recovery via a full restart, which kills open cursors. This test must instead force a from-disk recovery on a live node that is serving an open cursor.

Test must prove the forced recovery (and the filter) really executed on the cursor's node. We can assert before/after on serverStatus().shardingStatistics.collectionShardingMetadataStatistics.