Support passing PSPath to native commands

[SteveL-MSFT]

PR Summary

Add a new PSNativePSPathResolution Experimental Feature where if a PSDrive is passed to a native command and uses the FileSystem provider, then the resolved file path is passed to the native command. This means something like:

code temp:/test.txt

now works as expected. Also, on Windows, if the path starts with ~, then that will get resolved before passing to a native command. In both cases, the path is normalized to the directory separators for the relevant operating system. Note:

• if the path is not a psdrive nor ~ (on Windows), then path normalization doesn't occur
• if the path is in single quotes, then it's not resolved and treated as literal

PR Context

Fix #10675
Fix #11386

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): PSNativePSPathResolution
• User-facing changes
  • Not Applicable
  • OR
  • Documentation needed
    • Issue filed: Document passing PSPath to native commands MicrosoftDocs/PowerShell-Docs#5848
• 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. This may include:
    • Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode (which runs in a different PS Host).
    • Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.
    • Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).
    • Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).

[SteveL-MSFT]

@PoshChan retry macos

[PoshChan]

@SteveL-MSFT, successfully started retry of PowerShell-CI-macOS

[SteveL-MSFT]

@PoshChan retry windows

[PoshChan]

@SteveL-MSFT, successfully started retry of PowerShell-CI-Windows

[AndreHS2020]

Hi

[SteveL-MSFT]

@PoshChan please retry windows

[PoshChan]

@SteveL-MSFT, successfully started retry of PowerShell-CI-Windows

[anmenaga]

Added doc issue: MicrosoftDocs/PowerShell-Docs#5848

[ghost]

🎉v7.1.0-preview.3 has been released which incorporates this pull request.:tada:

Handy links:

• Release Notes