create_capped_collection_visibility_snapshot.js sets internalQueryExecYieldIterations to 1 to force more yields, making other concurrent tests slow.

One potential solution is to tag and exclude these tests from concurrency_simultaneous suite since they could have a performance impact to other tests. If there's a finer grained way to exclude them it would be nicer since we only observed one failure under debug tsan build.

Besides the tests that sets internalQueryExecYieldIterations to 1, there are also others that set it to 5 or 10. The choice seems arbitrary and we might want to review them to see if they're set at the right value, and whether the tests with higher values still need to be excluded.