[epic] Begin using DevWorkspace Operator container contributions functionality

[amisevsk]

Is your enhancement related to a problem? Please describe

DevWorkspace Operator PRs

• Add support for containerContributions devfile/devworkspace-operator#844
• Add support for contributions through .spec.contributions field in DevWorkspace devfile/devworkspace-operator#939
  Add a new field to DevWorkspaces and functionality to allow automatic merging of components in a DevWorkspace. This issue is to track the semi-coordinated work required across the dashboard and devfile registry to begin using this feature in DWO.

Describe the solution you'd like

The following tasks need to be semi-coordinated between dashboard and devfile registry. In addition, these changes should wait until the next DevWorkspace Operator release to ensure the functionality is available on the DWO side. DevWorkspace Operator v0.17.0 will be the first release to include .spec.contributions and the merge functionality.

• Dashboard should put plugins in DevWorkspace .spec.contributions instead of as plugin components in .spec.templates #21737
• Editor devfiles should use controller.devfile.io/container-contribution: true attribute on injectable components #21739
• Use DevWorkspace Operator contributions attributes to inject editors into Devfile containers #21738
• DevWorkspaces generated in che-devfile-registry build should use container contributions #21832
• Remove the DevWorkspace handler code from the Che-Code repository #21837
• Inject JetBrains in the devfile tooling container (as for VS Code) #21878