SERVER-135753Backlog
Investigate whether the execution ticket can be released independent of a nested non-global lock wait
* Problem: when an operation already holds a ticket (from an earlier, broader lock acquisition, e.g. the global lock) and then blocks waiting on a second, narrower lock (e.g. a $merge target collection lock, or $collStats with waitForLock: true), it keeps holding the ticket for the entire time it's blocked. Confirmed via repro (a 4.2-second lock wait produced 4,224ms of ticket delinquency with no interrupt-side signal at all). * This is a ticket delinquency-only issue; the interrupt side exe