[BUG] Rancher can no longer provision harvester machines after restart

[khushboo-rancher]

Describe the bug
This is in reference to the bug rancher/rancher#44912.
The issue is the cloud Credentials associated with a token has 30 days expiry by default. So, after 30 days if a user try to manage downstream cluster, they are unable to do that.

To Reproduce
Steps to reproduce the behavior:

1. Install Harvester (tested with v1.2.1, likely irrelevant)
2. Install Rancher (tested with v2.8.2, testing with other versions TBD)
3. Import Harvester cluster
4. Upload a suitable cloud image and create a VM network, so VMs can be created
5. To shorten the time to reproduce, set the default token TTL in Rancher to e.g. 10 minutes. This is a global config setting in Rancher.
6. Create a Cloud Credential for the Harvester cluster
7. Create a K8s cluster with the Harvester cluster as infrastructure provider, using the previously created Cloud Credential for authentication
8. Wait until the default token TTL is over. The token associated with the Cloud Credentials will be expired and eventually removed, but the Cloud Credential will remain. This will not cause an error just yet though.
9. Scale the K8s cluster from step 8 up or down. This operation will fail with behavior and errors similar to the reported problem.

Expected behavior
User should be able to manage their downstream clusters all the time once they have set Rancher with Harvester

Support bundle

Environment

• Harvester ISO version: v1.2.1, 1.2.2, 1.3.0
• Rancher - Anything after 2.8 i.e. 2.8.1, 2.8.2, 2.8.3

[David Ko]

This is independent from Harvester versions but assigned to 1.4.0, as it's the current working milestone.

[David Ko]

cc @Vicente-Cheng @FrankYang0529

[David Ko]

@m-ildefons will help with this issue validation when it's moved to ready for testing.