Test KubePlus deployment in non-default namespace

[devdattakulkarni]

Per this issue, we have tested KubePlus behavior when deployed in non-default namespace.

However, this code in mutating-webhook, indicates otherwise.

Let's test KubePlus behavior in non-default namespace again. If it works as expected then we should delete above code from webhook.go

[prathameshk03]

I tested this by deploying KubePlus in a non-default namespace (kubeplus).

The KubePlus pod came up fine in kubeplus namespace, and when I applied a service composition, the application instance was created in its own namespace (sample-odooservice).

$ kubectl get ns
NAME                 STATUS   AGE
default              Active   15m
kube-node-lease      Active   15m
kube-public          Active   15m
kube-system          Active   15m
kubeplus             Active   15m
sample-odooservice   Active   72s

This confirms that KubePlus behaves consistently regardless of whether it is deployed in the default namespace or a custom namespace as concluded in #1224. Each application still gets its own dedicated namespace.