AutoGetCollectionForRead uasserts if we have readConcern level snapshot and there have been catalog changes since the read timestamp. This does not occur for write commands, since they use AutoGetCollection instead of AutoGetCollectionForRead. Write commands must also perform this check, since they use/update indexes.

This will be less of a concern once speculative behavior is in place, since we will always use the locally committed snapshot. But it will still be essential for atClusterTime.