Currently, the tests written in this file have very specific assertions for test cases. This means that any changes to plan selection may result in the failure of this test, even if the new plan is valid. 

An example is BF-29709, which was caused by a change in multi-planner tie breaking. When this new heuristic is applied, the plans with CLUSTERED_IXSCAN is chosen over ones with FETCH, which resulted in the test failing, despite both plans being valid.

The refactor should ensure that the test passes for all valid plans, not just one of them. This will ensure changes in plan selection do not result in failure.

Point of contact is alexander.ignatyev@mongodb.com as katie.yang@mongodb.com will be off.