In SERVER-99150 we've implemented a lock ordering checker. This checker has detected a conflict in the ShardingCatalogManager class.

Inside of this class we have two lock orderings:

• Lock the _kClusterCardinalityParameterLock -> Lock the FCV lock due to a setClusterParameter sub-operation
• Lock the FCV lock -> Lock the _kClusterCardinalityParameterLock

We should investigate if there's a way to only have one ordering or if the current state is safe considering the FCV lock is taken in shared mode.