We currently sometimes check if the global lock was taken in a mode conflicting with writes to ensure that an operation will be killed during step up or step down (like here). However, that's no longer the only situation that we kill an opCtx anymore, so we should update those checks to call opCtx->shouldAlwaysInterruptAtStepDownOrUp() as well.