cursor_valid_after_shard_stepdown assumes that the secondary has no information about the collection on step up. In the max mirroring suite, though, the secondary can have an up to date view of the collection because of mirroring reads, and so the assertion that shardversion should be unknown after step up will not always be true.

We should prevent this test from running in the max mirroring suite, and provide a comment in the test about the problem, in case this causes issues for other tests and the assertion of unknown version needs to be removed.