Essentially the same format as the other safe secondary reads tests, but
this one has 4 drop/recreate scenarios that it puts each command
through:

• dropRecreateAsUnshardedOnSameShard
• dropRecreateAsShardedOnSameShard
• dropRecreateAsUnshardedOnDifferentShard
• dropRecreateAsShardedOnDifferentShard

There is a subtle relationship between shard versioning and using UUIDs,
because epochs are a pseudo-UUID that exist only for sharded
collections.

I see this as part testing, part documentation of our current
drop/recreate behavior, which is sans UUIDs.