(Subtask to achieve SERVER-84243 - Dedicate a catalog cache and loader to the shard role. For more information refer to this document)

Theoretically, no external users should access the CatalogCache via the FilteringMetadataCache because it should be a component only used for refreshing the filtering metadata in the CSR/DSS in an optimized way, and not a component to consult the contents of the cache, as there are no guarantees behind that data. If a user needs to consult the filtering metadata, it must consult it via the CSR/DSS.

Today, there is one call that accesses indirectly the CatalogCache in the migration_util.cpp file. By removing that call, we can remove the public method (`forceGetCurrentMetadata`) from the FilteringMetadataCache class.

The goal of this ticket is to remove the only call that indirectly exposes the CatalogCache content via the FilteringMetadataCache by updating the migrations code and rely on other public functions.