PR Summary

This pull request includes changes to the build configuration and deployment properties in the PowerShell.Common.props and build.psm1 files. The main goal is to refine the build and deployment process for different types of deployments.

Build and Deployment Configuration Improvements:

• PowerShell.Common.props: Added new property groups to handle different deployment types, specifically for Framework dependent deployments (FddPackage) and tools (FddTool). This includes setting the AppHostDotNetSearch property and handling the PublishReadyToRun property appropriately based on the deployment type.

• build.psm1: Updated the build script to pass the AppDeployment property, allowing the PowerShell.Common.props file to set the correct properties for different deployment types. This includes changes to handle FddTool and FddPackage deployments. [1] [2]

PR Context

This property is only for Mariner currently.
.NET tools are expected to respect DOTNET_ROOT. However, the package for Mariner should not use DOTNET_ROOT, but use a system defined dotnet runtime instead.
Self-Contained Deployments (SCD) installs don't support this new property.

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: