The solution to avoiding an uninterruptible lock in SERVER-61334 causes performance degradation in the insert_vector test. Experimentation shows that the issue is not the double-locking but rather the extension of the lock duration. This is because taking the global lock also takes the PBWM, which results in synchronizing the OplogBatcher to the OplogApplier.

We should not take the PBWM nor any WT tickets for this particular lock acquisition, and audit other GlobalLock uses added as part of FileCopyBasedInitialSync to see if they should also not take the PBWM or WT tickets.