ShardingCatalogManager::_updateClusterCardinalityParameter can fail due to ConflictingOperationInProgress when another ConfigsvrCoordinator is running concurrently. This is benign, but can cause transient glitches where add/removeShard fails. To prevent this, we can retry _updateClusterCardinalityParameter upon ConflictingOperationInProgress, similarly to what we already do for setAddOrRemoveShardInProgressClusterParam