checkCollectionMetadataInShardCatalog does some juggling of CSR acquisitions to try and defend itself from concurrent migration commits (or any chunk operation commit after auth shards). Instead, it should be cleaner to just establish a consistent snapshot and read the local and remote catalogs at the same timestamp, this way the function shouldn't care about any concurrent commit.

One potentially undesirable consequence of doing this is that the primary would be no longer reading from the latest changes of the CSRS, which is generally OK but may break when facing manual catalog repairs from the playbook.