In the stepdown suite, if the config server primary steps down during shardCollection just before sending setShardVersion to the primary shard, the primary shard may never receive setShardVersion, therefore never refresh its cache for the collection, and so not have an entry in its cache for the collection.

This causes the UUID check that compares the UUID on the config server with the UUID in a shard's cache to fail.

We should not perform this check in the stepdown suite, until it is guaranteed that a shard refreshes its cache after shardCollection.