[Infra] Trigger pipeline fail if help generation throws an error.

[DanielMicrosoft]

Description

Mandatory Checklist

• Please choose the target release of Azure PowerShell. (⚠️Target release is a different concept from API readiness. Please click below links for details.)

  • General release
  • Public preview
  • Private preview
  • Engineering build
  • No need for a release

• Check this box to confirm: I have read the Submitting Changes section of CONTRIBUTING.md and reviewed the following information:

• SHOULD update ChangeLog.md file(s) appropriately
  • Update src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md.
    • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header in the past tense.
  • Should not change ChangeLog.md if no new release is required, such as fixing test case only.
• SHOULD regenerate markdown help files if there is cmdlet API change. Instruction
• SHOULD have proper test coverage for changes in pull request.
• SHOULD NOT adjust version of module manually in pull request

[azure-client-tools-bot-prd]

Thanks for your contribution! The pull request validation has started. Please revisit this comment for updated status.

[DanielMicrosoft]

This commit will cause desired behaviour (pipeline fail on help generation error): 7128c98

But will attempt with pipeline config level fix.

[DanielMicrosoft]

Have cherry-picked the fix from release branch, to verify it will run green once help files are rectified.

[Copilot]

Pull Request Overview

This PR adds exit code validation to the analyze-steps.ps1 pipeline script to ensure that help generation and static analysis commands fail the pipeline appropriately when they encounter errors.

Key changes:

• Introduced a new Assert-ExitCodeSuccess helper function to validate exit codes
• Added exit code checks after help generation and static analysis operations