Overview

Two tests skip when featureFlagSbeFull is enabled because they rely on classic-engine-only failpoints that never fire under SBE full.

Affected Tests

* jstests/sharding/query/collmod_constraint_scan_with_chunk_migration.js — uses hangBeforeDocumentSourceCursorLoadBatch, which only fires on the classic DocumentSourceCursor path
* jstests/noPassthrough/query/prepare_constraint_blocks_invalid_wcos_updates.js — uses hangCollScanDoWork, which only fires on the classic collection scan path

Background

With featureFlagSbeFull enabled, the constraint validation scan's $match + $limit pipeline is fully lowered to SBE, bypassing DocumentSourceCursor entirely. The classic-engine failpoints never trigger, so the tests call quit() early on the SBE full variant.

See SERVER-128100 for the original fix.

Scope of Work

When featureFlagSbeFull ships, update these tests to use an equivalent SBE failpoint (e.g. hangScanGetNext) or a new batch-level SBE failpoint, so the concurrent chunk migration and WCOS update scenarios have coverage under the SBE full execution path.