[Feature]: PowerShell CLI Friendly

ITNOA

# Description of the new feature/enhancement

As you can know PowerShell is great Scripting Language for Automation and Administration of system. and it is built by Microsoft, so I think it is very good for WinApp CLI to get compatible with PowerShell and make native PowerShell [Cmdlet](https://docs.microsoft.com/en-us/powershell/scripting/lang-spec/chapter-13?view=powershell-7.1) to provide a native and consistent user experience in Microsoft Ecosystem.

# Proposed technical implementation details (optional)

I think PowerShell has many guideline and documentation about writing and designing great Cmdlet and modules that WinApp Dev CLI teams have to follow it for example

[Windows PowerShell Cmdlet Concepts](https://docs.microsoft.com/en-us/powershell/scripting/developer/cmdlet/windows-powershell-cmdlet-concepts?view=powershell-7.1)
[Writing a Windows PowerShell Module](https://docs.microsoft.com/en-us/powershell/scripting/developer/module/writing-a-windows-powershell-module?view=powershell-7.1)
[PowerShell Script Module Design: Building Tools to Automate the Process](https://mikefrobbins.com/2018/11/01/powershell-script-module-design-building-tools-to-automate-the-process/)
[Powershell: DSL design patterns](https://powershellexplained.com/2017-03-13-Powershell-DSL-design-patterns/)

Start by reviewing the existing WinApp CLI command architecture, then read the linked PowerShell Cmdlet Concepts and module-design guidance. The issue names no files, entry points, tests, or specific commands; completion would require an agreed scope for native cmdlets and a defined compatibility and acceptance test plan.

Written by the indexing model from the issue text.