After creating and sharding the config.system.sessions collection, there is a refresh that might not notice the creation of the sharded collection.

This happens because the catalog cache cannot be trusted in secondaries in the config server, specifically, if a config server secondary haven't replicated the write changes and tries to create the indexes then it will end up targeting the config server instead of the shards. We should ensure that the changes have been replicated, we could for example do a write after creating the collection and wait for that configOpTime, or, find a way to get the configOpTime gossiped by the create collection response.