After SERVER-95393 [Dedicate a catalog cache and loader to the shard role] work, the shard now uses a ConfigServerCatalogCacheLoader to refresh its routing information.

Currently, if a shard's routing information is stale during a transaction, the shard does not attempt to retry the operation. Instead, it raises a `StaleConfig` exception that will subsequently be retried at the driver level. This approach may be overly pessimistic, given that the shard—whether primary or secondary—can now refresh its routing information through the config server without needing to write anything to disk.

This ticket aims to track an investigation and possibly implement changes that would allow the shard to refresh its routing information and retry operations within the transaction.