We've updated the shardingStatistics field in serverStatus to accomodate new metrics:

• Critical section metrics for both collection and databases have been added which offer a gauge on how many operations hold the critical section, how many are waiting, and for how long they've been waiting/holding. These metrics are under the fields databaseCriticalSectionStatistics, and collectionCriticalSectionStatistics.
• Counters for updates to the sharding database version have been added that reflect how many sets/clears/access changes/durable changes have been made since the start of the server. These reside in databaseVersionUpdateCounters. NOTE: these are only active from FCV 8.3 onwards as they relate to a newly added feature.

Description of Linked Ticket

The goal of this ticket is to introduce new metrics in server status output to track the usage of collection critical section. 
The collection critical section is used to temporarily block CRUD operations on a collection while a DDL or data migration operations are committing collection metadata changes to global catalog and shard-local catalog.

------

Ideally, this ticket should be executed together with SERVER-99934.