[ws-daemon] - InitWorkspace error results in dispose error, causing INITIALIZING to fail

[kylos101]

Bug description

Here you can see ws-manager call initializeWorkspace, and then retryIfUnavailable:

Here you can see the chain of events that led to the retry, looks like a runInitializer got a 404:

Steps to reproduce

Not sure. Perhaps try deleting a branch as a workspace is being started, so after the context has been parsed, before the workspace starts doing content initialization?

Workspace affected

No response

Expected behavior

Not sure.

We may need to test content initialization, to see if there's a flow where we don't quite finish initializing, but still create state indicating that there's a workspace to dispose via its workspace.json file, where in reality, it never existed.

Example repository

No response

Anything else?

No response