PR Summary

Backport#24583

This pull request includes a series of updates to the.pipelines/PowerShell-Release-Official.yml and related templates to improve the build and release process. The most significant changes involve updating dependencies between stages, adding new steps for PowerShell installation, and removing obsolete templates.

Changes to dependencies and stages:

• Updated dependencies for various stages to ensure correct execution order, replacingPublishGitHubRelease withPushGitTagAndMakeDraftPublic in multiple stages.[1][2][3][4][5][6][7][8][9]
• AddeddependsOn: [] to several validation stages to clarify that they do not depend on any previous stages.[1][2][3][4]

New steps for PowerShell installation:

• Added a new task in therelease-install-pwsh.yml template to install PowerShell 7 and verify its installation.

Removal of obsolete templates:

• Removed outdated templates fromrelease-githubtasks.yml related to pushing git tags and making drafts public.

Minor updates and cleanups:

• Removed unnecessary variables and feature flags from thePowerShell-Release-Official.yml file.[1][2]
• Removed the step to download NuGet packages inrelease-publish-nuget.yml.

PR Context

PR Checklist

• PR has a meaningful title
  • Use the present tense and imperative mood when describing your changes
• Summarized changes
• Make sure all.h,.cpp,.cs,.ps1 and.psm1 files have the correct copyright header
• This PR is ready to merge and is notWork in Progress.
  • If the PR is work in progress, please add the prefixWIP: or[ WIP ] to the beginning of the title (theWIP bot will keep its status check atPending while the prefix is present) and remove the prefix when the PR is ready.
• Breaking changes
  • None
  • OR
  • Experimental feature(s) needed
    • Experimental feature name(s):
• User-facing changes
  • Not Applicable
  • OR
  • Documentation needed
    - [ ] Issue filed:
• Testing - New and feature
  • N/A or can only be tested interactively
  • OR
  • Make sure you've added a new test if existing tests do not effectively test the code changed
• Tooling
  • I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
  • OR
  • I have considered the user experience from a tooling perspective and opened an issue in the relevant tool repository. This may include:
    • Impact onPowerShell Editor Services which is used in thePowerShell extension for VSCode
      (which runs in a different PS Host).
      • Issue filed:
    • Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.
      • Issue filed:
    • Impact onPSScriptAnalyzer (which provides linting & formatting in the editor extensions).
      • Issue filed:
    • Impact onEditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).
      • Issue filed: