Compact in v6.0 we will still acquire the PBWM lock under the hood. As compact is a user operation, we don't opt out of `ShouldNotConflictWithSecondaryBatchApplicationBlock` and we will take the PBWM lock as part of acquiring the global lock here.

When SERVER-89727 was done, the PWBM lock was removed from the codebase (it no longer exists right now on master), but the PBWM lock still exists in 6.0. As a workaround for this, this ticket should opt out of the state before we obtain the global lock. Since compact simply rearranges blocks of data, having a consistent viewpoint of the data shouldn't matter with compaction.