Starting a full reindex while a bulk edit is running slows it down severely

Issue Summary

When we start a full re-index, existing bulk edit tasks continue running, but are slowed down to the point they look stuck.

This is reproducible on Data Center: yes

Steps to Reproduce

1. Start a large bulk edit
2. Start a full reindex before the bulk edit ends

Expected Results

If Jira gave a warning to the admins, for example, they could wait or choose another node to run the full re-index task.

Alternatively, Jira could cancel the ongoing tasks and throw an error saying a full reindex was started.

Actual Results

The bulk edit looks stuck, because it has to compete for the index lock with the reindex.

In the logs, we see timeouts when trying to acquire the index lock:

2023-01-30 21:47:47,325-0500 JiraTaskExecutionThread-51 ERROR user1 1234x65432x1 4aadqy 192.168.1.1 /secure/views/bulkedit/BulkEditPerform.jspa [c.a.j.issue.index.DefaultIndexManager] Wait attempt timed out - waited 30000 milliseconds
com.atlassian.jira.issue.index.IndexException: Wait attempt timed out - waited 30000 milliseconds
	at com.atlassian.jira.issue.index.DefaultIndexManager.obtain(DefaultIndexManager.java:905)
	at com.atlassian.jira.issue.index.DefaultIndexManager.access$600(DefaultIndexManager.java:101)
	at com.atlassian.jira.issue.index.DefaultIndexManager$IndexLock.tryLock(DefaultIndexManager.java:1247)
	at com.atlassian.jira.issue.index.DefaultIndexManager.getIndexLock(DefaultIndexManager.java:891)

Workaround

Either restart the node before starting a full re-index or check for tasks using the workaround from (JRASERVER-74796) Implement a way to check cluster tasks in execution