The executeComandAgainstDatabasePrimary function takes in a CachedDatabaseInfo object in order to route the command. If the caller is using a CollectionRouter loop, though, then they have likely already passed in a CollectionRoutingInfo object to the router loop.

To prevent this use case from needing to also fetch the database information from the cache, we should allow executeCommandAgainstDatabasePrimary to be called with a CollectionRoutingInfo object, since it already contains the dbPrimary and the dbVersion.