Support Powershell sessions via SSH

**Title**: Support for AksHci Powershell scriptlets via SSH

**Description**: Some of the AksHci Powershell commandlets like Set-AksHciConfig (and others) will not work when executed within a Powershell session over OpenSSH. For example, when running Set-AksHciConfig inside an SSH Powershell session (with administrator rights), it will show this error:

> WinRM service is already running on this machine.
> WinRM is already set up for remote management on this computer.
> Powershell remoting to MICROSO-97BAHKT was not successful.
> At C:\Program Files\WindowsPowerShell\Modules\Moc\0.2.25\Moc.psm1:2973 char:17
> + ... throw "Powershell remoting to "+$env:computername+" was n ...
> + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> + CategoryInfo : OperationStopped: (Powershell remo...not successful.:String) [], RuntimeException
> + FullyQualifiedErrorId : Powershell remoting to MICROSO-97BAHKT was not successful.

When opening a Powershell session via RDP with the same user, it works.

In general, all Powershell libraries should be tested with SSH sessions.

thanks,

Tobias Weisserth

Start by reproducing Set-AksHciConfig in an administrator PowerShell session over OpenSSH and compare it with the working RDP session. Inspect C:\Program Files\WindowsPowerShell\Modules\Moc\0.2.25\Moc.psm1 around line 2973, then determine how the SSH failure affects the other PowerShell libraries. Done means the affected commands work over SSH and the libraries have corresponding coverage.

Written by the indexing model from the issue text.