Description of problem:

When creating a spoke cluster, the UI does not perform proper validation to prevent duplicate node pool names. If a user adds two node pools with the same name (e.g., "pool1"), the initial UI validation passes, allowing the user to proceed. However, during provisioning, an error is thrown stating the node pool already exists. Despite this error, the spoke cluster provisioning is triggered in the backend, and the duplicate node pool name persists in the generated YAML configuration. This results in an inconsistent state where the UI shows an error, but the cluster creation process continues with invalid configurations.

Version-Release number of selected component (if applicable): 2.13.0-DOWNSTREAM-2025-01-26-13-48-39

How reproducible:

Steps to Reproduce:

1. Navigate to the cluster creation UI (e.g., Create cluster > Node pools).
2. Add a node pool (e.g., name: "pool1") and configure parameters (cores, memory, etc.).
3. Add a second node pool with the same name ("pool1").
4. Observe that the UI does not flag the duplicate name during input validation.
5. Click Create to provision the cluster.
6. UI displays an error: "1 nodepools.hypershift.openshift.io 'pool1' already exists."
7. Navigate to the Clusters page and observe that the spoke cluster provisioning is triggered, with the duplicate "pool1" entry retained in the YAML.

Actual results:

• UI allows duplicate node pool names during configuration.

• Provisioning fails with an error, but the cluster creation process starts anyway.

• Duplicate node pool names persist in the cluster’s YAML, leading to potential misconfigurations.

Expected results:

• UI validation should immediately flag duplicate node pool names and block submission.

• Cluster provisioning should not proceed until all node pool names are unique.

• A clear error message should guide the user to resolve the duplication before submission.

Snapshots:

When i click on Create -

After, when I visit clusters page -