Che-Code auto-opened terminal doesn't work (for `main` branch)

Describe the bug

The terminal widget that’s opened automatically on Che-Code start is not connected to machine-exec.

Note, that the terminal opened manually (from the dropdown menu) works as expected:

Che version

next (development version)

Steps to reproduce

Start a workspace with Che-Code editor.

Expected behavior

The auto-opened terminal should be ready to use.

Runtime

OpenShift

Screenshots

No response

Installation method

OperatorHub

Environment

Linux

Eclipse Che Logs

In the editor container:

time="2022-07-07T19:13:47Z" level=error msg="Unable to initialize terminal. Cause: container with name Terminal was not found."

### Additional context

_No response_

[pdfruth]

Answering my own question

Is there any way to work around this until a resolution is found? For example, Is there a way to explicitly set the image tag on the id: che-incubator/che-code/insiders in the che-editor.yaml file?

I have reconfigured my project’s .che/che-editor.yaml file from this;

id: che-incubator/che-code/insiders
registryUrl: https://eclipse-che.github.io/che-plugin-registry/main/v3

to this;

reference: https://<mygist>/che-editor.yaml

And the file at https://<mygist>/che-editor.yaml contains this; Notice: the explicit setting of image: quay.io/che-incubator/che-code:insiders-694ef6e refers to a previous version of the quay.io/che-incubator/che-code image, tagged approximately a day or so before the issue being reported above began to manifest

schemaVersion: 2.1.0
metadata:
  name: che-code
commands:
  - id: init-container-command
    apply:
      component: che-code-injector
events:
  preStart:
    - init-container-command
components:
  - name: che-code-runtime-description
    container:
      image: quay.io/devfile/universal-developer-image@sha256:53cec58dd190dd1e06100478ae879d7c28abd8fc883d5fdf5be3eb6e943fe5e7
      command:
        - /checode/entrypoint-volume.sh
      volumeMounts:
        - name: checode
          path: /checode
      memoryLimit: 1024Mi
      memoryRequest: 256Mi
      cpuLimit: 500m
      cpuRequest: 30m
      endpoints:
        - name: che-code
          attributes:
            type: main
            cookiesAuthEnabled: true
            discoverable: false
            urlRewriteSupported: true
          targetPort: 3100
          exposure: public
          path: '?tkn=eclipse-che'
          secure: false
          protocol: https
        - name: code-redirect-1
          attributes:
            discoverable: false
            urlRewriteSupported: true
          targetPort: 13131
          exposure: public
          protocol: http
        - name: code-redirect-2
          attributes:
            discoverable: false
            urlRewriteSupported: true
          targetPort: 13132
          exposure: public
          protocol: http
        - name: code-redirect-3
          attributes:
            discoverable: false
            urlRewriteSupported: true
          targetPort: 13133
          exposure: public
          protocol: http
    attributes:
      app.kubernetes.io/component: che-code-runtime
      app.kubernetes.io/part-of: che-code.eclipse.org
  - name: checode
    volume: {}
  - name: che-code-injector
    container:
      image: quay.io/che-incubator/che-code:insiders-694ef6e
      command:
        - /entrypoint-init-container.sh
      volumeMounts:
        - name: checode
          path: /checode
      memoryLimit: 128Mi
      memoryRequest: 32Mi
      cpuLimit: 500m
      cpuRequest: 30m

[azatsarynnyy]

To fix this issue we have disabled the Shell integration support in Che-Code (https://github.com/che-incubator/che-code/pull/90). After significantly reworking the remote terminals support (https://github.com/eclipse/che/issues/21626#issuecomment-1270057819), we’ve returned back the VS Code native terminal and enabled Shell integration by default (https://github.com/che-incubator/che-code/pull/124).