PR Summary

This pull request includes several changes to the Azure Pipelines YAML files, focusing on updating variables and references to improve consistency and functionality.

Key changes include:

Variable Updates:

• Updated theNetwork value fromNetlock toKS3 in theextends: section of the.pipelines/PowerShell-Release-Official.yml file.

Output Variables:

• Modified thesteps: in.pipelines/templates/release-SetReleaseTagandContainerName.yml to useOutputReleaseTag.ReleaseTag instead ofReleaseTag and addedisOutput=true to thevso[task.setvariable] command.
• Updated thejobs: in.pipelines/templates/release-create-msix.yml to useOutputVersion.AzureVersion instead ofAzureVersion.
• Added a new variable$releaseVersion in thejobs: section of.pipelines/templates/release-githubtasks.yml to strip the leading 'v' fromReleaseTag.
• Changed thejobs: in.pipelines/templates/release-validate-globaltools.yml to useOutputVersion.Version for both thedotnet tool install command and the version check.[1][2]
• Updated thejobs: in.pipelines/templates/release-validate-packagenames.yml to useOutputVersion.AzureVersion instead ofAzureVersion.
• Modified thejobs: in.pipelines/templates/release-validate-sdk.yml to useOutputVersion.Version instead ofVersion.

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: