Some tests in com.mongodb.internal.operation.AsyncQueryBatchCursorFunctionalSpecification are failing against a sharded cluster backed by PSS replica set shards (which are going to introduced soon in drivers-evergreen-tools).

I can reproduce this locally and I observe that in some cases a query is replied to with no data and also no cursorId. It looks to be related to the collection catalog, as the test repeatedly drops and re-creates the same collection, and if I run the tests in that class one at a time they pass.

I propose to disable these tests for pre-3.2 sharded clusters, rather than figure out the root cause. The rationale is that MongoDB 3.0 is no longer a supported server release, so it's not worth the effort.