SERVER-45983 simplified the way the shard version is refreshed in a shard by doing it on a separate thread and executing a migration recovery if needed, making sure we have a reliable shard version after a refresh.

To make sure that this new behavior is not causing a convoy of refresh threads if several concurrent operations hits the shard, we want to another test that should check the number of collection metadata refreshes before and after this situation.