When the aggregation machinery needs to fetch the collation for an untracked collection, a listCollections command is sent to the dbPrimary.
The problem is that we are not attaching the dbVersion to this listCollections command, therefore, if there is any change on the dbPrimary location, we may target the wrong shard without noticing it.

In case of targeting an old primary shard, we'll return the default collation.