[release-v2.8] Third chart batch release for Rancher v2.8.3

[lucasmlp]

Charts:

rancher-vsphere-cpi 103.1.0+up1.7.0 and rancher-vsphere-csi 103.1.0+up3.1.2-rancher1:

• [dev-v2.8] rancher-vsphere-csi/rancher-vsphere-cpi k8s 1.28 support #3386
• [dev-v2.8] Bump rancher-vsphere-csi to include a bugfix for CSI Snapshotter #3655
• [dev-v2.8] Revert vsphere csi changes #3663

rancher-provisioning-capi 103.1.0+up0.1.0:

• [v1.28] Update CAPI Chart #3367

rancher-cis-benchmark 5.1.0:

• Update role in cis-operator to manage prometheusrule resources #3188
• [dev-v2.8] Add EKS 1.2.0 in CIS Benchmark #3272
• [dev-v2.8] Add CIS-1.8 RKE, RKE2 and K3s templates and Update CIS-Benchmark Chart #3277
• [v2.8] Cis 1.7 benchmark: fix max kubernetes version #3312
• [v2.8] cis-benchmark chart k8s 1.28 support #3504
• [dev-v2.8] bump security scan #3593
• [dev-v2.8] CIS: update cis-operator and security-scan version #3610
• [dev-v2.8] unrc cis 5.1.0 chart #3665

fleet 103.1.1+up0.9.1:

• Update Fleet to v0.9.1-rc.2 #3350
• Update Fleet to v0.9.1-rc.4 #3478
• Update Fleet to v0.9.1-rc.5 #3515
• Update Fleet to v0.9.1-rc.6 #3586
• [dev-v2.8] Update fleet to 0.9.1 #3684
• Update Fleet to v0.9.2 #3689

Charts Checklist (built for v5.2.x charts-build-scripts)

Checkpoint 0: Validate release.yaml

Validation steps:

• Each chart version in release.yaml DOES NOT modify an already released chart. If so, stop and modify the versions so that it releases a net-new chart.
• Each chart version in release.yaml IS exactly 1 more patch version than the last released chart version. If not, stop and modify the versions so that it releases a net-new chart.

Checkpoint 1: Compare contents of assets/ to charts/

Validation steps:

• Running make unzip to regenerate the charts/ from scratch, then git diff to check differences between assets/ and charts/ yields NO differences or innocuous differences.

IMPORTANT: Do not undo these changes for future steps since we want to keep the charts/ that match the current contents of assets!

Checkpoint 2: Compare assets against index.yaml

Validation steps:

• The index.yaml file has an entry for each chart version.
• The index.yaml entries for each chart matches the Chart.yaml for each chart.
• Each chart has ALL required annotations
  • kube-version annotation
  • rancher-version annotation
  • permits-os annotation (indicates Windows and/or Linux)

[github-actions]

Validation steps

• Ensure all container images have repository and tag on the same level to ensure that all container images are included in rancher-images.txt which are used by airgap customers.

  Ex:-
    longhorn-controller:
      repository: rancher/hardened-sriov-cni
      tag: v2.6.3-build20230913
  

• Add a 👍 (thumbs up) reaction to this comment once done. CI won't pass without this reaction to the github-action bot's latest validation comment.
• Approve the PR to run the CI check.

[github-actions]

Validation steps

• Ensure all container images have repository and tag on the same level to ensure that all container images are included in rancher-images.txt which are used by airgap customers.

  Ex:-
    longhorn-controller:
      repository: rancher/hardened-sriov-cni
      tag: v2.6.3-build20230913
  

• Add a 👍 (thumbs up) reaction to this comment once done. CI won't pass without this reaction to the github-action bot's latest validation comment.
• Approve the PR to run the CI check.

[github-actions]

Validation steps

• Ensure all container images have repository and tag on the same level to ensure that all container images are included in rancher-images.txt which are used by airgap customers.

  Ex:-
    longhorn-controller:
      repository: rancher/hardened-sriov-cni
      tag: v2.6.3-build20230913
  

• Add a 👍 (thumbs up) reaction to this comment once done. CI won't pass without this reaction to the github-action bot's latest validation comment.
• Approve the PR to run the CI check.