The loadIndexesFromAuthoritativeShard helper currently assumes that if a collection has a routing table it is enough to just check for the shard version on the shard receiving the listIndexes command.

Since we're starting tracking unsharded collections on the sharding catalog (with a 1-chunk routing table), this path will be taken also for unsharded collections. This is going to trigger errors when a movePrimary happens because the db version changes but not the shard version, hence we may target the old primary and not find the necessary indexes.