Improve the sensitive history scrubbing to allow retrieving token from az, gcloud, and kubectl

[daxian-dbw]

PR Summary

Fix #3633
Improve the sensitive history scrubbing to allow retrieving token from az, gcloud, and kubectl.
The default sensitive history scrubbing was updated to handle retrieving token with gcloud, with Azure (both az cli and Az PowerShell), and with kubectl (both get secret and describe secret).

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

[andyleejordan]

I'm ok with this but wary of the precedent it sets for us to get this right not only for these commands, but for every possible ask in the future. Like it's a nice improvement...but I could see this growing huge if we don't have a plan to decide which commands we don't scrub (and do scrub). Perhaps we should have a more general way to allow users to add exceptions?

[daxian-dbw]

Perhaps we should have a more general way to allow users to add exceptions?

The user can already add exceptions, or customized scrubbing by Set-PSReadLineOption -AddToHistoryHandler { <a script block> } (see doc on this parameter). Here is an example that applies additional rules on top of the default: #2698 (comment). User can also choose to disable the scrubbing by Set-PSReadLineOption -AddToHistoryHandler $null.

The improvement made to the default scrubbing algorithm is for general scenarios that many users will run into. Otherwise, we will ask the user to apply the AddToHistoryHandler for their individual needs.

[ghost]

🎉 v2.3.1-beta1 has been released which incorporates this pull request. 🎉