PR Summary

As @PowerShell/powershell-committee had agreed that a native command writing to stderr is not an indicator of failure, it doesn't make sense to have $? to $false unless the native command also has a non-zero exit code. Fix is to move the setting of pipeline failure to the block only if the error record is not from a native command.

This is an addition to Experimental Feature PSNotApplyErrorActionToStderr.

PR Context

Fix #13393

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): PSNotApplyErrorActionToStderr
• User-facing changes
  • Not Applicable
  • OR
  • Documentation needed
    • Issue filed: $ErrorActionPreference doesn't affect stderr output for native commands MicrosoftDocs/PowerShell-Docs#6466
• 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).