PR Summary

This pull request introduces significant updates to the PowerShell release pipelines, focusing on automating MSIX package publishing, improving channel selection, and adding configurations for store submissions. The changes include new parameters, templates, and configuration files to streamline the release process.

Pipeline Enhancements for MSIX Publishing:

• AddedskipMSIXPublish parameter: A new boolean parameter was added to.pipelines/PowerShell-Release-Official.yml to allow skipping the MSIX publishing step during the release process.
• Replaced approval job with MSIX publish template: Updated thePublishMsix stage to use a newrelease-MSIX-Publish.yml template and conditionally skip publishing based on theskipMSIXPublish parameter.

Store Submission Configuration:

• CreatedPDP.xml for store metadata: Added a detailedPDP.xml file to define product descriptions, keywords, screenshots, and other metadata for the Microsoft Store submission.
• AddedSBConfig.json for StoreBroker: Introduced aSBConfig.json file to configure StoreBroker settings, including submission parameters, pricing, and device family support.

Channel Selection and Configuration Updates:

• IntroducedchannelSelection.yml template: Added a script to determine the release channel (LTS, Stable, or Preview) and set corresponding pipeline variables.
• Updated MSIX creation pipeline: Enhanced.pipelines/templates/package-create-msix.yml to include channel selection, update store configurations (PDP.xml andSBConfig.json), and automate StoreBroker package creation and upload.[1][2]

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