Route long indexing command to the Bulk Service keeping WM indexing near realtime

Outside of a full repository re-indexing case, there are actions like moving folder, changing ACL or deleting folder, that potentially trigger re-indexing of lots of documents.
When this happens other indexing activities are delayed and this impacts directly GUI experience, for instance, a created document is not indexed and cannot be viewed.

To avoid this we want to route all long indexing tasks into the bulk service, it acts as a separate indexing queue (distinct from the WorkManager indexing) avoiding delaying UI activity that requires near real time indexing.

Initial case description to handle ACL change

When an ACE is changed on a large folder (more than 500 documents) the Bulk service is used to materialize the Read ACL on the MongoDB side (since NXP-30426).
The Elastic index also needs a materialization of the Read ACL, this is an orthogonal process that is currently relying on the WorkManager.
Even if the Elastic update is reliable it uses the same indexing queue as the current activity and may delay too much its indexing.