Avoid selecting Helm beta and alpha releases

[sigv]

Description

Ref: microsoft/azure-pipelines-tasks#21287

There was just a Helm release of v4.0.0-alpha.1 and looking at v3.0.0-beta.5 we can expect the v4 releases to also do betas. These all should be skipped just like the release candidates (rc).

Use semver package's pre-release parsing, for easily identifying release candidates, betas and alphas. And then skip those specific pre-releases.

---

Package Name

azure-pipelines-tasks-kubernetes-common

---

Risk Assessment (Low / Medium / High)

Low. Semver specification is clear on how versions should be named, and Helm has been consistently applying those principles.

---

Unit Tests Added or Updated

• Unit tests added or updated
• Manual tests performed

---

Additional Testing Performed

Manual confirmation of logic.

---

Documentation Changes Required (Yes / No)

No. Users expect latest to be a stable release already.

---

Dependencies

No dependency changes.

---

Checklist

• Related issue linked (if applicable)
• Package version was bumped — see versioning guide
• Verified the package behaves as expected
• CLA signed (if applicable) — see Contributor License Agreement

---