Mark environment with stopped container as UNHEALTHY

[dilshat]

To make SS consistent with Hub we should mark environments where at least one container is not running as UNHEALTHY and disallow modifications of UNHEALTHY env-s.
Should we do this @absidish @samsonbek ?

[tzununbekov]

https://github.com/optdyn/hub/issues/3157

[dilshat]

I also think that STOPPED container does not mean UNHEALTHY environment.
Previously SS side marked env as UNHEALTHY only if something failed during environment creation or modification. The current problem is that if not all containers are running then we can not exchange SSH keys between new/running and existing stopped containers

[absidish]

we can not exchange SSH keys between new/running and existing stopped containers we need fix it, may be on start container check other containers keys and add ssh keys.

[dilshat]

Blocked by https://github.com/optdyn/hub/issues/3157