Context:
Whenever an ElasticsearchStatusException occurs e.g. during report evaluation it's catched and mapped to an error response via `ElasticsearchStatusExceptionMapper`.
The Optimize API error message contains the content of `message` from the original exception which is usually suffice for the Optimize API error response.

However it would be helpful to still log the full original ElasticsearchStatusException in the Optimize log for easier debugging in such cases.

AT:

• when an ElasticsearchStatusException occurs the `ElasticsearchStatusExceptionMapper` should log the full original exception