Provide stack for Apache Camel K in Dev File registry

[apupier]

Is your enhancement related to a problem? Please describe.

Apache Camel K development is currently complicated.
it will be a bit easier with the Camel K plugin in the registry #14806 but it remains 2 complicated tasks:

• set kubeconfig
• create a Camel K instance

Describe the solution you'd like

I would like to have a stack which have:

• an example with a Cmael K files (to choose either one file or several file sof the potentialdsl groovy, xml, java, yaml, javascript, kotlin)
• a Camel K instance running
• the kubeconfig preconfigured to access the Camel K instance

Camel K is provided via an operator on Kubernetes/OpenShift. it can be installed using kamel cli with kamel install call

Describe alternatives you've considered

Additional context

[apupier]

for the example, it will be convenient to just point to the example folder in official Camel K repo when it will possible (soon) #13671

[apupier]

currently the kamel CLI is using the service account of the launched container and not the user defined in kubeconfig. apache/camel-k#1048
The service account doesn't have enough rights to even launch a Camel K integration.

[apupier]

The first iteration has been provided, the stack contains:

• VS Code extensions for Camel K, Kubernetes, XML and Apache Camel
• kubectl and kamel on container terminal
• examples based on the official camel-k-examples

It doesn't contain:

• a Camel K instance running. This is something that requires several improvements on Che/Kubernetes side (support of Operator Lifecycle Manager in devfile?) it won't be available on short-term/middle-term
• a preconfigured kubeconfig, this is something generic to Che, see Improve kubeconfig injection with chectl #14877 +the configuration needs to be redone on each workspace start

Based on that, when using the Stack:
user needs to log to a Kubernetes cluster on which Camek K runtime is installed or can be installed, some potential ways:
-- chectl workspace:inject -k (if you're locally logged to on and Che is installed locally)
-- open terminal in the workspace, create ~/.kube/config with content retrieved from kubectl config view --raw --flatten --minify command launched in a place where you are logged in
in case Camel K is not yet installed AND you have enough rights
-- switch to che namespace (can be done through Kubernetes perspective in Clusters --> -> Namespaces --> right-click on che --> Use Namespaces)
-- open terminal from the vscode-camelkXXX container in the workspace and call kamel install
Then you can right-click on one of the Camel K files (for instance simple.groovy) and choose "Start Apache Camel K Integration" and then choose "Basic mode" type, after few seconds/minutes, the panel Apache Camel K integrations of Explorer perspective should have another entry called simple with a green dot
Be patient for the first runs, it takes time for first deployment and to have the correct feedback in Apache Camel K integrations (can be up to few minutes)