Dashboard should better handle devworkspace startup failure

[sleshchenko]

Describe the bug

Dashboard should better handle devworkspace startup failure.

1. When DevWorkspace becomes failed it's still displayed as Starting:
   
2. After tab is changed, the state is rerendered but the INFO is not propagated:
   
3. When DevWorkspace has failed state, it's not possible to update DevWorkspace:
   

DevWorkspace to test:

schemaVersion: 2.0.0
metadata:
  name: spring-petclinic
  namespace: opentlc-mgr-che
components:
  - container:
      env:
        - name: ENV_VAR
          value: value
      image: 'quay.io/eclipse/che-java8-maven:nly'
      memoryLimit: 1536M
      sourceMapping: /projects
      volumeMounts:
        - name: mavenrepo
          path: /root/.m2
    name: maven
  - name: mavenrepo
    volume:
      size: 1G

Che version

• latest
• nightly
• other: please specify

Steps to reproduce

Expected behavior

Runtime

• kubernetes (include output of kubectl version)
• Openshift (include output of oc version)
• minikube (include output of minikube version and kubectl version)
• minishift (include output of minishift version and oc version)
• docker-desktop + K8S (include output of docker version and kubectl version)
• other: (please specify)

Screenshots

Installation method

• chectl
  • provide a full command that was used to deploy Eclipse Che (including the output)
  • provide an output of chectl version command
• OperatorHub
• I don't know

Environment

• my computer
  • Windows
  • Linux
  • macOS
• Cloud
  • Amazon
  • Azure
  • GCE
  • other (please specify)
• Dev Sandbox (workspaces.openshift.com)
• other: please specify

Eclipse Che Logs

Additional context

[nickboldt]

Not resolved for 7.34/7.35, so slip to 7.36. If that's an error, please fix.