workspace-loader doesn't recognize when workspace start fails immediately after start request is sent

[garagatyi]

Description

When because of some reason workspace start request succeeds but start itself fails immediately after that wsmaster send event with error to subscribed websocket clients.
But workspace-loader doesn't receive it because it subscribes only after that message was already sent.
Which leads to a infinitely running loading screen with no error shown

It seems that workspace-loader subscribes to workspace status event after sending workspace start request, not before that.

Reproduction Steps

OS and version:

Diagnostics:

[garagatyi]

@vitaliy-guliy FYI

[vitaliy-guliy]

Thanks!

[rhopp]

@akurinnoy Shouldn't this issue be reopened, as the commit was reverted?

[akurinnoy]

@rhopp sure, thanks!