dynamic services are being closed without user intervention

[GitHK]

On deployments where we do not have a policy for services to be closed down automatically (like osparc.io), after a period of inactivity, we are observing that users report issues with service being closed out of the blue without their intervention.

The issue

Services are unexpectedly closed by the garbage collector. There are multiple reports for the issue like:

• Rogue Garbage Collector osparc-simcore#6087
• Random dynamic service disconnection #1616

Other issues which makes above situation worse

1. the platform does not properly report that the services has been shut down. Services still appear to be in (blue tick) running status. There is already an issue for this (Service state driven by the backend #1175). Work is in progress (backend PR) but was paused due to other higher priorities. It will still require followup PRs.

2. Platform does not notify users and platform does not log the reasons why a service was closed. This makes supporting user harder since it's very hard to figure out what triggered a service to close.

[GitHK]

TN's service406fe863-34d5-45d5-8cd1-1524c1337827 was hit by this at 7:13 UTC today. No FE call to close the service only other plausible cause is GC.

[GitHK]

this can be closed since it's similar to ITISFoundation/osparc-simcore#6087