PR Summary

This pull request introduces several changes to the macOS packaging process, including updates to the build scripts and dependencies. The most significant changes involve adding a new packaging stage, removing the ronn dependency, and updating the man page generation process.

macOS Packaging Process:

• Added a new PackageMac stage to the .vsts-ci/mac.yml file, which depends on the BuildMac stage and includes steps for macOS packaging using PowerShell. (.vsts-ci/mac.yml)

Dependency Management:

• Removed the ronn dependency from the Start-PSBootstrap function in build.psm1 and the Get-PackageDependencies function in tools/packaging/packaging.psm1. (build.psm1) [1] (tools/packaging/packaging.psm1) [2]

Man Page Generation:

• Updated the man page generation process to use roff instead of ronn in the New-ManGzip function in tools/packaging/packaging.psm1. (tools/packaging/packaging.psm1)
• Added a new man page for pwsh in assets/manpage/pwsh.1. (assets/manpage/pwsh.1)

PR Context

macOS man page generation is failing. Checking in asset so we can get the release working.

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: