Today, the collMod coordinator broadcasts `shardsvrCollModParticipant` to all shards in the cluster. The coordinator will parse each shard response depending if that shard owns any chunk.

If we move an unsharded collection from its db primary shard, making that collection tracked and, behind the scenes, an unsplittable collection with one chunk placed in another shard, and we run a collMod, we may end up with inconsistent collection options.

The collmod coordinator will target the shard that contains the only chunk - processing its successful response - and the db primary shard that contains locally the collection but without chunks - ignoring its error response.

That is, we have created a collection options mismatch inconsistency.