Disallow saving a non-opened project

[odeimaiz]

What do these changes do?

When a user forgets a project opened in a laptop, or takes a plane. the project gets disconnected after 15 minutes.
In case he reconnects, the project would save again without being opened in the backend. This cannot be tolerated.

Solution:
when the connect/reconnect event happens in the webscoket, the frontend asks for the active study. If the backend already closed the study, it will return a null. In that case the frontend brings the user back to the dashboard.

Related issue/s

related to ITISFoundation/osparc-issues#435

How to test

Checklist

[codecov]

Codecov Report

Merging #2225 (8d769b7) into master (dc5cf7c) will decrease coverage by 0.0%.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           master   #2225     +/-   ##
========================================
- Coverage    73.0%   72.9%   -0.1%     
========================================
  Files         465     465             
  Lines       17983   17983             
  Branches     1773    1773             
========================================
- Hits        13133   13124      -9     
- Misses       4381    4387      +6     
- Partials      469     472      +3     

Flag	Coverage Δ
integrationtests	65.3% <ø> (-0.2%)	⬇️
unittests	66.4% <ø> (+<0.1%)	⬆️

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

Impacted Files	Coverage Δ
...webserver/computation_comp_tasks_listening_task.py	84.9% <0.0%> (-6.5%)	⬇️
...ce_webserver/resource_manager/garbage_collector.py	74.8% <0.0%> (-1.0%)	⬇️
...erver/src/simcore_service_webserver/director_v2.py	85.0% <0.0%> (-0.9%)	⬇️

[sanderegg]

Cool. Maybe a short message telling the user he was disconnected for too long might come in nicely?

[pcrespov]

Shouldn't we add a condition on the backend API such that a study can only be modified if it is first active (i.e. opened) ?

[odeimaiz]

Shouldn't we add a condition on the backend API such that a study can only be modified if it is first active (i.e. opened) ?

The problem is that at the moment the frontend can't patch a specific field in the study, so every modification in the study itself goes through the put call providing the whole serialized study in the body, not only the workbench changes.... (that's why the very first solution from Friday was discarded).
This means that, right now, you should be able to update a study (e.g. add a classifier) even if it's not open.

[GitHK]

I see, we'll have to provide a better solution for the future.