Issues when a devfile is invalid and Che fails gracefully

[l0rd]

Describe the bug

I have been trying the feature "Handle gracefully when an invalid devfile is found in a git repository" and I have spotted a few problems.

1. If I "continue with the default devfile" then the resulting devworkspace doesn't have an editor nor an UDI container and as a result fails to start

$ kubectl get devworkspace vscode-switch-pt5r -o json | jq .spec.template.components
[
  {
    "attributes": {
      "che.eclipse.org/default-plugin": true
    },
    "name": "default-f00c9bc0a1587654ccb8",
    "plugin": {
      "uri": "https://static.developers.redhat.com/crw/stg/plugins/devworkspace-telemetry-woopra-plugin/0.0.1/devfile.yaml"
    }
  }
]

2. The error message is hard to read

Che version

7.55@latest

Steps to reproduce

Open https://che-dogfooding.apps.che-dev.x6e0.p1.openshiftapps.com/#https://github.com/l0rd/che-operator/tree/a4f1949c33ddab5f66c19c27a844af1c46aa0820 on your browser.

Expected behavior

1. The workspace should start when I select "continue with the default devfile".
2. I expect the default devWorkspce to have the default editor and default container (UDI).
3. The error message should render well so that I am able to read it.

Additional context

I have been testing on the dogfooding instance.

[l0rd]

I am using Firefox