To start JetBrains IDEs, use post-start rather than overrideing the entrypoint

[l0rd]

Is your enhancement related to a problem? Please describe

The editor command overrides the tooling container entrypoint:

• if the user had specified the container command in his devfile
• if the tooling container had a specific entrypoint + command

This blocks services as kubedock (to support docker run) to be run at startup in tooling containers.

Describe the solution you'd like

The solution is the same as the one provided for VS Code, remove the command in the editor container and a an init-che-code-command among the devfile commands associated to a post-start event:

(...)
  commands:
      - id: init-che-code-command
        exec:
          component: che-code-runtime-description
          commandLine: 'nohup /checode/entrypoint-volume.sh > /checode/entrypoint-logs.txt 2>&1 &'
  events:
      postStart:
        - init-che-code-command

[devstudio-release]

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

• feat: Use post-start event to start JetBrains IDEs che-plugin-registry#1623
• feat: Use post-start event to start JetBrains IDE redhat-developer/devspaces#922