[BUG] Modify local-rke-state secret to allow upgrade from previous version

[bk201]

Describe the bug

Rancher will check the secret, and upgrading RKE2 will fail.
The change causes it: rancher/rancher#41088
Related rancherd issue: rancher/rancherd#29, we need to make sure new clusters have the right secret too.

To Reproduce

• Upgrade to a newer Harvester version contains the Rancher change.

Expected behavior

Support bundle

Environment

• Harvester ISO version:
• Underlying Infrastructure (e.g. Baremetal with Dell PowerEdge R630):

Additional context
Add any other context about the problem here.

[harvesterhci-io-github-bot]

Pre Ready-For-Testing Checklist

• ~If labeled: require/HEP Has the Harvester Enhancement Proposal PR submitted?
  The HEP PR is at:~~

• Where is the reproduce steps/test steps documented?
  The reproduce steps/test steps are at: fix(upgrade): change type of local-rke-state secret #4050

• Is there a workaround for the issue? If so, where is it documented?
  The workaround is at:

• Have the backend code been merged (harvester, harvester-installer, etc) (including backport-needed/*)?
  The PR is at: fix(upgrade): change type of local-rke-state secret #4050 fix(upgrade): change type of local-rke-state secret (backport #4050) #4060

  • Does the PR include the explanation for the fix or the feature?

  • Does the PR include deployment change (YAML/Chart)? If so, where are the PRs for both YAML file and Chart?
    The PR for the YAML change is at:
    The PR for the chart change is at:

• If labeled: area/ui Has the UI issue filed or ready to be merged?
  The UI issue/PR is at:

• If labeled: require/doc, require/knowledge-base Has the necessary document PR submitted or merged?
  The documentation/KB PR is at:

• If NOT labeled: not-require/test-plan Has the e2e test plan been merged? Have QAs agreed on the automation test case? If only test case skeleton w/o implementation, have you created an implementation issue?

  • The automation skeleton PR is at:
  • The automation test case PR is at:

• If the fix introduces the code for backward compatibility Has a separate issue been filed with the label release/obsolete-compatibility?
  The compatibility issue is filed at:

[harvesterhci-io-github-bot]

Automation e2e test issue: harvester/tests#854

[irishgordo]

This looks good 😄 👍
Tested upgrade from v1.1.2 -> master-173b0824-head

Looking at secret after upgrade, via: kubectl get secrets local-rke-state -o yaml -n fleet-local
Noting:

apiVersion: v1
data:
  agentToken: dG9rZW4=
  serverToken: dG9rZW4=
kind: Secret
metadata:
  annotations:
    field.cattle.io/projectId: local:p-n7s5k
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"v1","data":{"agentToken":"dG9rZW4=","serverToken":"dG9rZW4="},"kind":"Secret","metadata":{"annotations":{"field.cattle.io/projectId":"local:p-n7s5k"},"creationTimestamp":"2023-06-22T19:03:29Z","name":"local-rke-state","namespace":"fleet-local","resourceVersion":"129156","uid":"b7ea30a0-0024-4d92-83e8-d8ab01c66127"},"type":"rke.cattle.io/cluster-state"}
  creationTimestamp: "2023-06-22T21:09:59Z"
  name: local-rke-state
  namespace: fleet-local
  resourceVersion: "132410"
  uid: 19fba33b-4d49-4dc1-befa-fb8ee562e220
type: rke.cattle.io/cluster-state

I'll go ahead and close this out 😄