Currently All deleteBy/updateBy in the application use the synchronous api of the elastic rest client. This may cause issues in certain environments on long running requests in combination with configured request timeouts on the elastic side. We already encountered this in the course of SUPPORT-9303.
Similar to like how all upgrade calls were adopted to use the asynchronous REST client API with
OPT-4524 we should also adopt to that API within the `ElasticsearchWriterUtil` that offers methods to execute deleteBy/updateBy queries.
- deleteBy/updateBy queries utilize the async execution api of elasticsearch to avoid the risk of hitting http request timeouts on long running requests.