fix: set proper ccm & csi maximum version

[guangbochen]

IMPORTANT: Please do not create a Pull Request without creating an issue first.

Problem:
The current default value is invalid, as it will prevent users from successfully selecting the Harvester cloud provider when creating or modifying the RKE2 Kubernetes cluster.

Solution:
Update the CSI & CCM maximum supported versions (We will bump the chart minor release version if it contains a significant design change). e.g.,

Harvester version	RKE2 with old CCM design	RKE2 with new CCM design( v0.2 - #2134)
>= v1.2	Supported	Supported
< v1.2	Supported	Not Supported

Related Issue:
#3404

Test plan:

• import an existing Harvester cluster(e.g., v1.1.2-rc3) into a Rancher server (>= v2.6.9 or v2.7)
• spin up a guest RKE2 k8s cluster(>= v1.24.10); its built-in Harvester CCM chart version is v0.1.14, and users can still select the Harvester cloud provider, but its configured harvester-csi-ccm-versions setting value is "harvester-cloud-provider":">=0.0.1 <0.1.14".
• replace the ui-dashboard-index value in the Rancher global setting page - request it from @n313893254
• you should not be able to select the Harvester cloud provider as the UI validation is enabled with the above modification.
• update the Harvester management chart, and patch the Harvester API server with a custom image(or patch the Harvester default setting value manually to {"harvester-cloud-provider":">=0.0.1 <0.2.0","harvester-csi-provider":">=0.0.1 <0.2.0"})
• now, you should be able to select the Harvester cloud provider correctly.

[yaocw2020]

LGTM, thanks

[guangbochen]

@mergify backport v1.1

[mergify]

backport v1.1.

❌ No backport have been created

• Backport to branch v1.1. failed

GitHub error: Branch not found

[mergify]

backport v1.1

✅ Backports have been created

• #3713 fix: set proper ccm & csi maximum version (backport #3710) has been created for branch v1.1