PR Summary

This pull request introduces several updates to pipeline configurations and templates to improve functionality, maintainability, and clarity. The changes include removing unused stages, refining file paths, enhancing release notes generation, and improving PowerShell script robustness. Below are the most important changes grouped by theme:

Pipeline Configuration Updates:

• Removed theReleaseDocker stage from.pipelines/PowerShell-Release-Official.yml to streamline the pipeline and eliminate unused functionality.
• Updated the file path for theSetVersionVariables.yml template in.pipelines/PowerShell-vPack-Official.yml to use a consistent relative path (.pipelines/templates/SetVersionVariables.yml@self).

Release Notes Enhancements:

• Enhanced the release notes generation in.pipelines/templates/release-githubNuget.yml by appending SHA256 hashes of release artifacts to the changelog using aStringBuilder. This ensures better traceability of release files.

PowerShell Script Improvements:

• Improved the robustness of theCopy-Item operation in.pipelines/templates/release-create-msix.yml by adding a check to ensure the destination directory exists before copying files.
• Replaced inline PowerShell scripts withPowerShell@2 tasks in.pipelines/templates/release-githubNuget.yml for better readability and alignment with modern Azure DevOps practices.[1][2]

Miscellaneous Updates:

• Added a title to the GitHub release task in.pipelines/templates/release-githubNuget.yml to clearly label the release with the version tag (e.g., "v1.0.0 Release of PowerShell").

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. If this PR is a work in progress, please open this as aDraft Pull Request and mark it as Ready to Review when it is ready to merge.
• 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