Discuss deployment in non-kubeflow namespace

[NohaIhab]

Description

There's a new environment variable added in kubeflow dashboard called POD_NAMESPACE this env variable enables the dashboard to be deployed in any namespace, not just kubeflow like it was hardcoded in the past, see this change. The same is applicable for kfp, see this change. We need to discuss whether we should support deployment in a namespace other than kubeflow, now that it seems to be unblocked by upstream, and whether it will be part of the 1.8 release.

@DnPlas suggested that in order to take on this effort, we need to:

• ensure all kubeflow components can now be deployed in any namespace
• remove the namespace check in some of our charms
• remove the hardcoded namespace in our templates and/or charm code (if any)