[backport v2.13.6] [BUG] RKE2 Cluster Template reuses previous cluster state instead of creating a new cluster

[rancher-ui-project-bot]

This is a backport issue for #17211, automatically created via GitHub Actions workflow initiated by @momesgin

Original issue body:

Rancher Server Setup

• Rancher version: v2.13.2 / v2.13.4 (Tested on both versions, 2.13.2 on community and prime, v2.13.4 tested on prime)
• Installation option (Docker install/Helm Chart): Helm Chart
  • If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc): RKE2
• Proxy/Cert Details: letsencrypt no proxy

Information about the Cluster

• Kubernetes version: v1.34.4+rke2r1
• Cluster Type (Local/Downstream): Local
  • If downstream, what type of cluster? (Custom/Imported or specify provider for Hosted/Infrastructure Provider):

User Information

• What is the role of the user logged in? (Admin/Cluster Owner/Cluster Member/Project Owner/Project Member/Custom) Admin
  • If custom, define the set of permissions:

Describe the bug
When using Rancher RKE2 Cluster Templates, creating a second cluster from the same template does not behave as expected. Instead of initializing a new cluster creation flow, Rancher reuses the state of the previously created cluster.

To Reproduce

1. Navigate to Cluster Management in Rancher
2. Click “Create Cluster”
3. Select an existing RKE2 Cluster Template (based on the official template)
4. Fill out the required template questions
5. Create the first cluster (Cluster 1) – this works as expected
6. Repeat the process to create a second cluster (Cluster 2) using the same template

Result

• The form is pre-filled with values from Cluster 1
• The UI displays the Helm release name of Cluster 1 in the title
• Instead of showing an “Install” button, the UI shows “Save Changes” (as if editing an existing cluster)
• Modifying values and proceeding causes Cluster 1 to be deleted and replaced with Cluster 2

Expected Result
A fresh, empty form should be displayed when creating a new cluster from the template.
Clicking “Install” should create a new, independent cluster (Cluster 2) without modifying or deleting Cluster 1.

Screenshots
Example of how the Cluster Template Installation page should look like (Install)

Example of broken Cluster Template Installation page (Save changes instead of Install)
Note the wrong title (release of Cluster 1 instead of Chart Name and the wrong button at the end)

Additional context

• In the template we use vSphere as provider type
• The template is based on the official RKE2 Cluster Template and has not been recently modified
• The issue occurs consistently across multiple environments
• This setup has worked correctly in the past
• The issue can be temporarily resolved by changing the chart name or chart version in the cluster template
  After such a change, one new cluster can be created successfully before the issue reoccurs

[izaac]

Rancher version: v2.13.6-alpha3
Rancher UI version: v2.13.6-alpha2
AWS provider.

The issue is no longer reproducible. The first install with the template shows the Install button as well as some empty fields mixed with defaults of the chart.
Install works and the provisioning starts.
Clicking in Create Cluster and selecting the cluster templates open the create view and the button is Install as expected after the fix.
The values continue to be a mix of defaults plus empty fields expected to be provided by the user.
With the correct values clicking install the provisioning start as expected.
Further provisioning with the templates continue behaving correctly.