Inject JetBrains in the devfile tooling container (as for VS Code)

[l0rd]

Is your enhancement related to a problem? Please describe

Today we have different behaviors for different IDEs:

• VS Code and its extensions are copied in a volume and started in the first devfile container.
• Theia runs in an isolated container but its plugins run are copied in a volume and run in the first devfile container.
• JetBrains IDEs and their extensions are run an isolated container.

Describe the solution you'd like

Theia and IntelliJ should be "contributed" to the first devfile container as it's currently done for VS Code. They should both:

• be packaged in an injector image that copies the IDE binary in a volume at startup
• should include 2 components in their YAML definition: the injector (init-container) and the runtime (contributions to the tooling container)

Additional context

Part of:

• [epic] Begin using DevWorkspace Operator container contributions functionality #21736

Related to:

• Rework Che-IDEA image to sidecar-less model #20863
• New workspace model to run VS Code as a Che editor #20435
• To start VS Code, use post-start rather than overriding the entrypoint #21879

[l0rd]

Closing as everything is completed