Allow an admin to specify Che default editor and containers

[l0rd]

Is your enhancement related to a problem? Please describe

If no devfile is present in a git repository the default is to start a workspace with only one component (the Theia container) and Theia as the editor.

That's a bad UX as the Theia container misses many langue tools and because an admin cannot change this behavior.

Describe the solution you'd like

The default container should be a UDI container. Both the default container and the default editor should be configurable in the CheCluster CR.

(...)
workspaces:
  (...)
  defaultComponent or defaultContainer ?: |
    name: universal-developer-image
    container:
        image: quay.io/devfile/universal-developer-image:ubi8-latest
        memoryRequest: 256M
        memoryLimit: 1536M
        cpuRequest: 0.1
        cpuLimit: 0.5
  defaultEditor: eclipse/che-theia/next
(...)

Additional Context

This is a #21340 subtask.

Release Notes Text

Che administrators can now configure the default editor (Theia, VS Code, IntelliJ or PyCharm) and the default container. Those defaults are used when the developer doesn't specify an editor or doesn't specify a devfile. The configuration can be done in the CheCluster Custom Resource in the the workspaces section using the just introduced defaultComponent and defaultEditor fields.

[amisevsk]

Another option for the new field in the CR is to use []devfile.Component rather than string. This would enable k8s validation of the field, devfile/api docs/autocomplete, etc. but would have the downside of making the CheCluster CR quite a bit bigger.

(...)
workspaces:
  (...)
  defaultComponents:
    - name: universal-developer-image
      container:
          image: quay.io/devfile/universal-developer-image:ubi8-latest
          memoryRequest: 256M
          memoryLimit: 1536M
          cpuRequest: 0.1
          cpuLimit: 0.5
    - name: some-volume
      volume: {}
  defaultEditor: eclipse/che-theia/next
(...)

The benefit of this approach would be that since both the Che Operator and Dashboard depend on devfile/api already, these components could be easily deserialized by both as needed and just added to empty devfiles directly, under .components

[l0rd]

@olexii4 the che operator PR has been merged and I am wondering why this issue is still open. Is it because you are working on a dashboard PR? I am asking because we would like to include it in the new and noteworthy features of this release.

[olexii4]

feat: support workspace defaults eclipse-che/che-operator#1395

PR was merged yesterday in the evening. I waited until the next image has built. I tried to test it. Today I have deployed CHE on minikube but cannot see changes that should be in che-operator. I am investigating the problem.

I will do my best to do it ASAP.

[nickboldt]

add comment to reset sync date, so we should get a new message here that collects the PRs.

[nickboldt]

comemnt

[devstudio-release]

sync'd to Red Hat JIRA https://issues.redhat.com/browse/CRW-3863

• feat: support workspace defaults che-operator#1395
• Add workspaces default editor and components che-dashboard#567

[amisevsk]

The beauty of automation 😂