kamel CLI - Allow to specify a namespace to use instead of default

[davsclaus]

Instead of installing Camel K in the default namespace which can get crowded, its nice to install it in a different namspace.

But then you need to have -n mykamel for all the CLI commands to operate on this namespace.

I wonder if we can have the CLI set a namespace to use

[squakez]

What about if we mimick kubectl CLI? If you want to stick to a namespace you must runt kubectl config set-context --current --namespace=default this would change the kube config file. I think we don't have any kamel config file, but we could use env vars or if it makes sense creating a config file to serve the scope.

[github-actions]

This issue has been automatically marked as stale due to 90 days of inactivity.
It will be closed if no further activity occurs within 15 days.
If you think that’s incorrect or the issue should never stale, please simply write any comment.
Thanks for your contributions!

[essobedo]

Should be fixed by #3599