PR Summary

This pull request introduces changes to enable MSBuild binary logging and improve the handling of build artifacts in the pipeline configuration and build scripts.

Pipeline Configuration Changes:

• .pipelines/PowerShell-Coordinated_Packages-Official.yml: Added a new parameter ENABLE_MSBUILD_BINLOGS to enable or disable MSBuild binary logs.
• .pipelines/PowerShell-Coordinated_Packages-Official.yml: Updated variables section to include the new ENABLE_MSBUILD_BINLOGS parameter.

Build Script Enhancements:

• build.psm1: Modified the Restore-PSPackage function to append the -bl argument for binary logging if ENABLE_MSBUILD_BINLOGS is set.
• build.psm1: Enhanced the Restore-PSPackage function to handle and upload MSBuild binary logs if a restore operation fails and ENABLE_MSBUILD_BINLOGS is enabled.

PR Context

Binary logs are much more readable but are too big to use all the time.

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: