Skip the AST analysis when command-line input has any parsing errors

[daxian-dbw]

PR Summary

Fix #3066

Skip the AST analysis when command-line input has any parsing errors in the default sensitive history scrubbing function.
When a command-line input matches sensitive pattern and has parsing error, we don't further analyze its AST because we cannot reliably do so with incorrect ASTs. In that case, we just consider it sensitive, given that it contains matches of our sensitive patterns.

PR Checklist

• PR has a meaningful title
  • Use the present tense and imperative mood when describing your changes
• Summarized changes
• Make sure you've added one or more new tests
• Make sure you've tested these changes in terminals that PowerShell is commonly used in (i.e. conhost.exe, Windows Terminal, Visual Studio Code Integrated Terminal, etc.)
• User-facing changes
  • Not Applicable
  • OR
  • Documentation needed at PowerShell-Docs
    • Doc Issue filed:

Microsoft Reviewers: Open in CodeFlow

[daxian-dbw]

@andschwa Please review when you have time, thanks!

[ghost]

🎉 v2.2.0-beta5 has been released which incorporates this pull request. 🎉