During the mongos startup, we perform a catalog cache load of all the collection's routing tables as an optimization to avoid the refresh delay on the first queries targeting this mongos.

However, this doesn't include the loading of the database metadata (see SERVER-86671 for further detail), which is needed to target an unsharded untracked collection.

Since the mongos is already being proactive in fetching the routing information, we should also include a call to the getDatabaseWithRefresh to precache the db metadata as well.