The suite sharded_collections_jscore_passthrough_with_config_transitions.yml runs our jscore tests with the config server transitioning in and out of config shard mode, which requires draining its sharded collections. This means the suite has many moveChunks, so tests that use fast count, which doesn't filter orphans since it's meant to be an estimate, can read incorrect values. The suite should disable tests that use it.