Platform-aware Install-PSResource: filter runtimes by RID, libs by TFM

[jshigetomi]

PR Summary

This pull request introduces platform-aware filtering to the package installation process, ensuring that only the most relevant files for the user's runtime and platform are extracted from NuGet packages. It adds new parameters to allow explicit selection of target runtime and framework, and implements logic to filter out unnecessary files, significantly reducing installation size and improving cross-platform support.

Platform-aware installation and filtering:

• Added RuntimeIdentifier and TargetFramework parameters to the InstallPSResource cmdlet, allowing users to specify the desired platform and framework for filtering package contents.
• Enhanced the extraction logic in InstallHelper.cs to filter runtimes and lib/ entries in .nupkg files, installing only those matching the detected or specified RID and TFM, and skipping unrelated files. [1] [2]
• Implemented methods to determine the best matching TFM (GetBestLibFramework), filter library entries (ShouldIncludeLibEntry), and auto-detect the current runtime's framework (GetCurrentFramework).

User experience and diagnostics:

• Added a warning (WarnIfCrossLineageTfmSkipped) when TFM filtering skips assemblies for a different .NET lineage, alerting users if the installed module may not work on another host (e.g., installing for PowerShell 7+ but skipping Windows PowerShell 5.1 assemblies).

PR Context

Platform aware installation was brought up in issue: #794.

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
  • Documentation needed
    • Issue filed:
• 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 enumerated concerns in the summary.