Update filter condition for HelmInstaller Tasks to filter out pre-releases

[sanjays-ms]

Context

HelmInstaller Pipeline Tasks is fetching alpha releases when task input is checkLatestHelmVersion: true
Updated the filter condition to fetch stable released versions
WI: AB#2334528
Fixes: #21287

---

Task Name

HelmInstallerV0, HelmInstallerV1

---

Description

HelmInstaller Pipeline Tasks is fetching alpha releases when task input is checkLatestHelmVersion: true
Updated the filter condition to fetch stable released versions

Update the related common package
microsoft/azure-pipelines-tasks-common-packages#509

---

Risk Assessment (Low / Medium / High)

Low

---

Change Behind Feature Flag (Yes / No)

Can this change be behine feature flag, if not why?

---

Tech Design / Approach

• Design has been written and reviewed.
• Any architectural decisions, trade-offs, and alternatives are captured.

---

Documentation Changes Required (Yes/No)

Indicate whether related documentation needs to be updated.

• User guides, API specs, system diagrams, or runbooks are updated.

---

Unit Tests Added or Updated (Yes / No)

Indicate whether unit tests were added or modified to reflect these changes.

---

Additional Testing Performed

Testing done through canary test pipelines as part of CI checks
https://dev.azure.com/canarytest/PipelineTasks/_build/results?buildId=221814&view=results
https://dev.azure.com/canarytest/PipelineTasks/_build/results?buildId=221813&view=results

---

Logging Added/Updated (Yes/No)

• Appropriate log statements are added with meaningful messages.
• Logging does not expose sensitive data.
• Log levels are used correctly (e.g., info, warn, error).

---

Telemetry Added/Updated (Yes/No)

• Custom telemetry (e.g., counters, timers, error tracking) is added as needed.
• Events are tagged with proper metadata for filtering and analysis.
• Telemetry is validated in staging or test environments.

---

Rollback Scenario and Process (Yes/No)

• Please revert PR to revert changes

---

Dependency Impact Assessed and Regression Tested (Yes/No)

• All impacted internal modules, APIs, services, and third-party libraries are analyzed.
• Results are reviewed and confirmed to not break existing functionality.

---

Checklist

• Related issue linked (if applicable)
• Task version was bumped — see versioning guide
• Verified the task behaves as expected

[sanjays-ms]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[sanjays-ms]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[sanjays-ms]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[sanjays-ms]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[benoittgt]

I made similar one in #21437

[sanjays-ms]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).