PR Summary

This pull request includes changes to various pipeline YAML files to update the naming conventions for builds. The most important changes include modifying the name parameter in several files to follow a new naming pattern.

Updates to naming conventions:

• .pipelines/PowerShell-Coordinated_Packages-Official.yml: Changed the name parameter to bins-$(BUILD.SOURCEBRANCHNAME)-$(Build.BuildId).
• .pipelines/PowerShell-Packages-Official.yml: Added the name parameter with the value pkgs-$(BUILD.SOURCEBRANCHNAME)-$(Build.BuildId).
• .pipelines/PowerShell-Release-Official-Azure.yml: Added the name parameter with the value ev2-$(BUILD.SOURCEBRANCHNAME)-$(Build.BuildId).
• .pipelines/PowerShell-Release-Official.yml: Added the name parameter with the value release-$(BUILD.SOURCEBRANCHNAME)-$(Build.BuildId).
• .pipelines/PowerShell-vPack-Official.yml: Modified the name parameter to vPack_${{ parameters.architecture }}_$(date:yyMM).$(date:dd)$(rev:rrr).

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: