Fixed release pipeline errors and switched to KS3

[jshigetomi]

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 the Network value from Netlock to KS3 in the extends: section of the .pipelines/PowerShell-Release-Official.yml file.

Output Variables:

• Modified the steps: in .pipelines/templates/release-SetReleaseTagandContainerName.yml to use OutputReleaseTag.ReleaseTag instead of ReleaseTag and added isOutput=true to the vso[task.setvariable] command.
• Updated the jobs: in .pipelines/templates/release-create-msix.yml to use OutputVersion.AzureVersion instead of AzureVersion.
• Added a new variable $releaseVersion in the jobs: section of .pipelines/templates/release-githubtasks.yml to strip the leading 'v' from ReleaseTag.
• Changed the jobs: in .pipelines/templates/release-validate-globaltools.yml to use OutputVersion.Version for both the dotnet tool install command and the version check. [1] [2]
• Updated the jobs: in .pipelines/templates/release-validate-packagenames.yml to use OutputVersion.AzureVersion instead of AzureVersion.
• Modified the jobs: in .pipelines/templates/release-validate-sdk.yml to use OutputVersion.Version instead of Version.

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 not Work in Progress.
  • If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending 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 on PowerShell Editor Services which is used in the PowerShell 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 on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).
      • Issue filed:
    • Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).
      • Issue filed:

[TravisEz13]

/azp run PowerShell-CI-linux

[azure-pipelines]

Azure Pipelines could not run because the pipeline triggers exclude this branch/path.

[TravisEz13]

/azp run PowerShell-CI-macos

[azure-pipelines]

Azure Pipelines could not run because the pipeline triggers exclude this branch/path.

[TravisEz13]

/azp run PowerShell-CI-static-analysis

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[TravisEz13]

/azp run PowerShell-CI-windows

[azure-pipelines]

Azure Pipelines could not run because the pipeline triggers exclude this branch/path.

[TravisEz13]

/azp run PowerShell-Windows-Packaging-CI

[azure-pipelines]

Azure Pipelines could not run because the pipeline triggers exclude this branch/path.

[microsoft-github-policy-service]

📣 Hey @jshigetomi, how did we do? We would love to hear your feedback with the link below! 🗣️

🔗 https://aka.ms/PSRepoFeedback

Microsoft Forms