Include Tooling for Apache Camel K VS Code extension in plugin registry

[apupier]

Is your enhancement related to a problem? Please describe.

it is currently almost impossible to develop a Camel K integration

Describe the solution you'd like

First step will be to provide the "Tooling for Apache Camel K" VS Code extension.

Describe alternatives you've considered

Additional context

The extension requires the Kubernetes one. it also requires to have kubectl and kamel CLI installed.

Started to work on it with:

• plugin configuration https://github.com/apupier/che-plugin-registry/blob/camelk/v3/plugins/redhat/vscode-camelk/0.0.9/meta.yaml
• DockerFile used by the plugin https://github.com/apupier/che-docker-files/blob/forChristina/camelk/Dockerfile It is based on the Dockerfiel iused for VS Code Kubernetes extension in Che. it already have kubectl then. Just adding kamel CLI
• modify local workspace devfile to use it

- reference: >-
      https://raw.githubusercontent.com/apupier/che-plugin-registry/camelk/v3/plugins/redhat/vscode-camelk/latest/meta.yaml
    memoryLimit: 1G
    type: chePlugin

currently blocked by the combination of bugs:

• error on refresh for custom meta.yaml Error: Failed to load plugins: Erro:request "getDeployedPluginIds' when a plugin is provided with a reference to meta.yaml file #14805 fixed
• problem with Kubernetes plugin clusters view is empty [k8s plugin] Clusters view is empty #14748 fixed
• requires a refresh to have left icon available [Openshift Connector] OpenShift Connector is not available after first workspace starting #14611

for reference in Fuse Tooling tracker https://issues.jboss.org/browse/FUSETOOLS2-16

In another iteration having a Camel K runtime instance pre-configured would be even better (through a specific stack?)