[BUG] - Changing namespace shouldn't result in cluster destruction/recreation

[Adam-D-Lewis]

Describe the bug

Setting

project_name: nebari10
namespace: prod

results in a kubernetes cluster with the name nebari10-prod. Changing the namespace should be possible, but b/c the namespace is contained in the cluster name it causes the cluster to be destroyed and recreated. This should be avoided since it's entirely valid to change the namespace without wanting to destroy the cluster.

Expected behavior

See above

OS and architecture in which you are running Nebari

linux x86-64

How to Reproduce the problem?

see above

Command output

No response

Versions and dependencies used.

No response

Compute environment

None

Integrations

No response

Anything else?

No response

[Adam-D-Lewis]

I think the biggest issue with fixing this will be handling existing users who already have a cluster with the namespace in the name.