Update package pipeline windows image version

[jshigetomi]

• Change package docker image version to 2022 latest
• Use Windows Host Version 2022 KS3

PR Summary

This pull request includes several changes to the pipeline configuration files to update container images, enable new feature flags, and modify job parameters. The most important changes are grouped by theme below.

Pipeline Configuration Updates:

• .pipelines/PowerShell-Packages-Official.yml: Updated the WindowsContainerImage variable to use the latest Docker image for Windows LTSC 2022.
• .pipelines/PowerShell-Packages-Official.yml: Added a new feature flag for WindowsHostVersion with version 2022 and network KS3.

Job Parameter Modifications:

• .pipelines/templates/checkAzureContainer.yml: Changed the azurePowerShellVersion input from latestVersion to LatestVersion and added a new parameter pwsh: true to enable PowerShell Core.

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:

[jshigetomi]

/azp run

[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