Document/Backport support SHA-256 thumbprints when connecting to the vSphere API

[lubronzhan]

What would you like to be added?

Document the support of SHA-256 on 1.30+, also backport to previous branch if needed

Why is this needed?

golang 1.24 is deprecating sha1 signiture kubernetes/kubernetes#125689
govmomi also starts to support sha256 thumbprint in 0.36.1. https://github.com/vmware/govmomi/releases/tag/v0.36.1

CPI used to support sha1 vsphere cert thumbprint to validate certificate. only 1.30 and main branch use govmomi 0.37.3, need to backport/document to other previous version if needed

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten