This check  was initially part of PM-2030 but we discarded the idea because we could get some false positives reports due to the low guarantees of refineShardKey operation.

The goal of this task is to implement a new sharding hook that it is run at the end of the sharding test and that verifies that what the config server authoritative believes shards own is exactly what shards believe they own. In other words, assuming that we have placement stability (no more operations ongoing (not even moveChunks)), we should verify that the different shard versions that are persisted on config.collections and config.chunks match whatever we have locally in each CollectionShardingRuntime of each shard. 

The getShardVersion command exposes the information on the CSR.

We should have a way to disable it.