Describe the bug
When deploying configuration for clusters, updating values such as name or id results in the creation of a new pointer while the old one remains. There appears to be no actual validation when modifying or removing a cluster.

Details
Conductor version:
dependencies:

• name: console
  repository: https://helm.conduktor.io
  version: 1.14.0

To Reproduce
Steps to reproduce the behavior:

Navigate to the configuration file.
Modify config.clusters by adding a new registry entry.
Deploy the configuration.
Modify id or name of an existing cluster.
Deploy again.
Observe that instead of updating the existing cluster, a new pointer is created while the old one still remains.

Expected behavior
Changes to cluster properties (e.g., id or name) should be validated properly to ensure that updates do not create redundant pointers. The old cluster entry should be replaced or removed when changes are made.

Screenshots

Additional context
clusters:

• id: 'example'
  name: 'example'
  bootstrapServers: "something:port"
  properties: |
  security.protocol=SASL_SSL
  sasl.mechanism=SCRAM-SHA-512