In ReshardingDonorRecipient we force a refresh of the database routing cache in order to fetch latest databse info.

The downside of forcing a cache refresh is that all the other subsequent database cache lookup will need to serialize behind the forced refresh.
To avoid this, we could use the CatalogClient to fetch the database information directly from the cluster catalog, bypassing the CatalogCache.

I attempted to do this as part of SERVER-95750, but unfortunately switching from CatalogCache to CatalogClient requires some adjustments to ReshardingDonorRecipientCommonTest unit tests.