What does this PR do?

Turns out we were swallowing uncaught exceptions raised during the execution of the tasks submitted via Executor#execute, ExecutorService#submit or ScheduledExecutorService#schedule calls, because the behavior is like the following:

• If uncaught exception is raised for task submitted via Executor#execute, then worker thread is killed and exception is printed to the console.
• If uncaught exception is raised for task submitted via ExecutorService#submit or ScheduledExecutorService#schedule, then worker thread is kept running and exception is thrown on the thread is which doing Future#get call (normally the thread getting the result). We were always ignoring the Future returned after the task is submitted, so we were swallowing such exceptions.

This change closes this gap by adding the hook to the ThreadPoolExecutor#afterExecute method, which allows to observe such uncaught exceptions. ThreadPoolExecutor#afterExecute is called on the thread which did the actual task execution.

The logic of this hook is taken from the afterExecute documentation.

Exceptions will be sent to the devLogger and to the internal telemetry as well.

Review checklist (to be filled by reviewers)

• Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
• Make sure you discussed the feature or bugfix with the maintaining team in an Issue
• Make sure each commit and the PR mention the Issue number (cf the CONTRIBUTING doc)