Without it eks or gke versions will not be considered as valid versions

Related to #401

What problem does this PR solve?

Helm relies on Masterminds/semver for version comparison. According to both the Helm docs and the SemVer README (see the "Checking Version Constraints" section), version ranges do not match pre-release versions unless the constraint explicitly allows them.

EKS (and GKE) Kubernetes versions always include a pre-release suffix, e.g.: v1.34.1-eks-3025e55. So, with a constraint like >= 1.19, SemVer will not consider pre-release versions valid, so Helm rejects the chart even though the Kubernetes version is technically higher.

The SemVer documentation explains that to include pre-releases in a version range, you must add a -0 suffix: >= 1.19.0-0

After changing the chart’s kubeVersion to include .0-0, Helm correctly accepted the EKS version.

Check List (For Author)

• Test

  • Regression test
  • Unit Test
  • Manual test (add detailed scripts or steps below)
  • No need to test or manual test. Explain why:
    • This is a refactor/code format and no logic has been changed.
    • Previous test can cover this change.
    • No code files have been changed.
    • Other reason

• Behavior changed:

  • No.
  • Yes.

• Does this need documentation?

  • No.
  • Yes.

Check List (For Reviewer who merge this PR)

• Confirm the release note
• Confirm test cases
• Confirm document
• Add branch pick label