PR Summary

This pull request includes multiple changes across various pipeline and workflow files to enhance the environment capture process by improving the output formatting. The most important changes involve updating the Get-ChildItem command to include additional formatting options for better verbosity and readability.

Environment Capture Improvements:

• .github/workflows/codeql-analysis.yml: Modified the Get-ChildItem command to use Out-String -width 9999 -Stream and write-Verbose -Verbose for capturing the environment.
• .pipelines/PowerShell-vPack-Official.yml: Updated the Get-ChildItem command to include Out-String -width 9999 -Stream and write-Verbose -Verbose for better environment capture.
• .pipelines/templates/SetVersionVariables.yml: Enhanced the environment capture by adding Out-String -width 9999 -Stream and write-Verbose -Verbose to the Get-ChildItem command.
• .pipelines/templates/linux-package-build.yml: Improved the environment capture by modifying the Get-ChildItem command to use Out-String -width 9999 -Stream and write-Verbose -Verbose.
• .pipelines/templates/mac-package-build.yml: Enhanced the environment capture with Out-String -width 9999 -Stream and write-Verbose -Verbose in the Get-ChildItem command.

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: