Fixed harvester chart values not being set

[eva-vashkevich]

Summary

Fixes #16857

As part of Traefik changes, I broke the logic around updating charts. This change revert it to the previous state.

Occurred changes and/or fixed issues

Technical notes summary

Areas or cases that should be tested

Attempt to provision a harvester cluster.
Validate that request contains 'harvester-cloud-provider' configuration under spec.rkeConfig.chartValues

Areas which could experience regressions

RKE2 and K3s provisioning could be affected. In particular, recently added Ingress configuration

Screenshot/Video

Checklist

• The PR is linked to an issue and the linked issue has a Milestone, or no issue is needed
• The PR has a Milestone
• The PR template has been filled out
• The PR has been self reviewed
• The PR has a reviewer assigned
• The PR has automated tests or clear instructions for manual tests and the linked issue has appropriate QA labels, or tests are not needed
• The PR has reviewed with UX and tested in light and dark mode, or there are no UX changes
• The PR has been reviewed in terms of Accessibility
• The PR has considered, and if applicable tested with, the three Global Roles Admin, Standard User and User Base

[Copilot]

Pull request overview

This PR fixes a regression in the Harvester cluster provisioning flow where chart values (e.g., harvester-cloud-provider) were not being set in spec.rkeConfig.chartValues. The bug was introduced during Traefik-related changes that incorrectly replaced direct property assignments with Vue 2-style reactive setters (this.set()), which inadvertently broke the chart values update logic.

Changes:

• Replaces Object.keys(this.versionInfo).forEach((key) => delete this.versionInfo[key]) with a simpler this.versionInfo = {} for clearing the version info cache on Kubernetes version change.
• Replaces this.set(this.versionInfo, chartName, res), this.set(this.userChartValues, key, {}), and this.set(this.userChartValues, key, different) with direct property assignments, matching the pre-regression behavior.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[a110605]

Tested on new created cluster. The LB creation flow is good.

Test Steps:

1. Import a harvester into rancher (1.7.x or 1.8.0 is fine)
2. Create a downstream harvester cluster
3. Go to Cluster -> Worload -> Deployment, create a nginx pod (container image : nginx:latest)

4. Add label `name: mynginx` in that pod

5. Go to Service Discovery -> Service - > Create

• Service port : myport / 8080 / 80
• Selector : name / mynginx

6. The LB should be successfully created.

[a110605]

LGTM