sharded_multi_stmt_txn_jscore_passthrough and its disagg variants wrap every statement in a retryable multi-document transaction via network_error_and_txn_override.js and replays operations on failure. getMore calls can't be enclosed in a transaction in this suite, because if a WriteConflict forces the transaction to be replayed (as happened here with the "Unable to write to collection 'config.transactions' due to catalog changes" errror) then it re-executes the getMore without knowing whether the cursor was already advanced or not. Attempting to reuse a stale cursor id produces the CursorNotFound error seen in BF-45727.

The solution is to exclude requires_getmore from this suite as is done in several similar retryable transaction suites (eg. multi_shard_multi_stmt_txn_jscore_passthrough).