♻️✨ Improve logging output in case of error when scheduling tasks

[sanderegg]

What do these changes do?

• the dask clients pool was reporting invalid errors with a valid cause in the client, thus generating confusion
• the traceback of the error was missing making it difficult to narrow down the issue

This PR shall help in fixing this.

Related issue/s

How to test

Checklist

[codecov]

Codecov Report

Merging #2842 (7832ba5) into master (0e9a59a) will decrease coverage by 0.1%.
The diff coverage is 42.8%.

@@           Coverage Diff            @@
##           master   #2842     +/-   ##
========================================
- Coverage    78.8%   78.7%   -0.2%     
========================================
  Files         674     674             
  Lines       27356   27352      -4     
  Branches     3185    3182      -3     
========================================
- Hits        21573   21537     -36     
- Misses       5023    5051     +28     
- Partials      760     764      +4     

Flag	Coverage Δ
integrationtests	65.7% <42.8%> (-0.1%)	⬇️
unittests	74.3% <42.8%> (-0.1%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
...e_service_director_v2/modules/dask_clients_pool.py	92.7% <33.3%> (+2.2%)	⬆️
...rector_v2/modules/comp_scheduler/base_scheduler.py	83.3% <100.0%> (+0.1%)	⬆️
...vice_director_v2/modules/dynamic_sidecar/errors.py	82.6% <0.0%> (-17.4%)	⬇️
...c/simcore_service_catalog/core/background_tasks.py	68.0% <0.0%> (-13.9%)	⬇️
...imcore_service_catalog/db/repositories/projects.py	41.6% <0.0%> (-12.5%)	⬇️
...ore_service_director_v2/api/routes/computations.py	80.1% <0.0%> (-2.6%)	⬇️
...tor_v2/modules/dynamic_sidecar/scheduler/events.py	93.1% <0.0%> (-1.8%)	⬇️
..._director_v2/modules/dynamic_sidecar/client_api.py	80.7% <0.0%> (-1.5%)	⬇️
.../director/src/simcore_service_director/producer.py	61.6% <0.0%> (-1.3%)	⬇️
...car/src/simcore_service_dask_sidecar/dask_utils.py	89.6% <0.0%> (-1.1%)	⬇️
... and 2 more

[odeimaiz]

👌

[pcrespov]

so now every other exception is just "let-go" ... who is handling it then?

[sanderegg]

the scheduler