PR Summary

This pull request includes several changes to various pipeline YAML files and the addition of a new PowerShell script. The changes mainly focus on modifying pipeline sources and removing unnecessary PowerShell module installation tasks.

Pipeline source updates:

• Updated the source ofCoOrdinatedBuildPipeline from 'PowerShell-Coordinated Packages-Official' to 'PowerShell-Coordinated Binaries-Official' in.pipelines/PowerShell-Packages-Official.yml[1].pipelines/PowerShell-Release-Official-Azure.yml[2] and.pipelines/PowerShell-Release-Official.yml[3].

Removal of unnecessary tasks:

• Removed the task to update theAz.Storage module in.pipelines/templates/checkAzureContainer.yml.
• Removed the task to install PowerShell modules in.pipelines/templates/compliance/apiscan.yml.
• Removed the task to install and uninstall PowerShell modules in.pipelines/templates/compliance/generateNotice.yml.
• Removed the task to removeAzureRM modules and installAz.Storage in.pipelines/templates/release-MakeBlobPublic.yml[1][2].pipelines/templates/release-create-msix.yml[3].pipelines/templates/release-upload-buildinfo.yml[4].pipelines/templates/release-validate-packagenames.yml[5] and.pipelines/templates/uploadToAzure.yml[6].

Addition of a new PowerShell script:

• Addedtools/installPSResources.ps1 to handle the installation of specific PowerShell modules from either the PSGallery or a custom feed.

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: