[BUG] Cluster conflict problem with the same cluster name

[groobyming]

Describe the bug
If you create two storage clusters with the same name but different types (e.g., MySQL and StarRocks), the later StarRocks cluster will overwrite the earlier MySQL cluster configuration, making the MySQL cluster unavailable.

To Reproduce
Steps to reproduce the behavior:

1. Create a MySQL storage cluster named mycluster following the official documentation.

2. Perform operations such as scaling, disk scaling, stopping, starting, restarting, and connecting to MySQL on the mycluster cluster. Ensure the cluster status is running and all operations complete successfully.

3. Attempt to create another storage cluster named mycluster using StarRocks by following the official documentation. Note the error encountered due to the duplicate name, and check the current status of the existing mycluster cluster.

4. Rename the StarRocks cluster to mycluster-doris and recreate it. Verify the statuses of both the mycluster (MySQL) and mycluster-doris (StarRocks) clusters.

5. Delete the mycluster-doris cluster and confirm that the status of the original mycluster cluster remains normal.

6. Attempt to reconnect to the mycluster cluster and note the failure. Review the error messages and inspect the details of the mycluster cluster to diagnose the issue

Expected behavior
If a cluster named clusterA for storage A already exists, creating another cluster named clusterA for storage B is not allowed.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [linux]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Additional context
【kbs and k8s version】:
Kubernetes: v1.32.0
KubeBlocks: 0.9.2
kbcli: 0.9.2

[shanshanying]

While applying the second cluster of the same name,

This mysql cluster goes abnormal. Do not use APPLY in such scenario. And KubeBlocks will add more constarints to avoid such changes.