Dynamic clusters self deleting on renames & old name still available

[vyncent-t]

Describe the bug

When using the add cluster button, adding resources from one kubeconfig file is flakey. (Users have reported it self deletes)

Adding an additional batch of resources from another kubeconfig, then renaming a resource, removes the initial kubeconfig and also keeps the previous rename as an available link.

To Reproduce

Import clusters from a location (kubeconfigA) then import from another location (kubeconfigB)

Initial
 
clusterA1
clusterA2
clusterB1
clusterB2
 
Renamed:
clusterB1 -> clusterB1-renamed
 
After:
 
clusterB1-renamed
clusterB1
clusterB2

Steps to reproduce the bug:

1. Open headlamp in app mode
2. Click add cluster button at home view
3. Click and add clusters from a kubeconfig
4. Return to home page and click add cluster button again
5. Add additional resources from a different kubeconfig
6. Return to homepage and rename one of the new resources
7. Notice that the initial resources vanish
8. Also notice the previous rename cluster name still available

Environment (please provide info about your environment):

• Installation type: Linux
• Headlamp Version: 0.31.1

Are you able to fix this issue?

No current fix yet

Additional Context

Experienced by other users #2979 (comment)

[vyncent-t]

could be related to #3498