Some locks acquired/release by the internal sharding machinery are "hot" because user operations may be impacted when the acquisition/release is delayed because of tickets unavailability. An example of sensible path is the acquisition/release of the critical section.

Purpose of this task is to identify such hot paths and consider using ScopedAdmissionPriorityForLock in order to bypass ticketing, similarly to what has been committed under SERVER-76835 to avoid unnecessarily blocking metadata refreshing.