Add PowerShell script and a helper class to deploy DevSetupAgent service to a Hyper-V VM.

[sshilov7]

Add PowerShell script and a helper class to deploy DevSetupAgent service to a Hyper-V VM.

Summary of the pull request

• Add DevSetupAgentDeploymentHelper helper class to handle deployment of DevSetupAgent to a Hyper-V VM.
  Provided Hyper-V admin credentials and a path to DevSetupAgent (folder with binaries or a .zip file) it will

1. Connect to the target Hyper-V device.
2. Copy file to the device
3. Remove old DevSetupAgent service if it exists
4. Copy DevSetupAgent binaries to $env:ProgramFiles\DevSetupAgent (or to the location of the old dervice)
5. Register DevSetupEngine COM server
6. Register DevSetupAgent Windows service
7. Start DevSetupAgent service.

• Add an integration test that can call DevSetupAgentDeploymentHelper with user's credential and path to DevSetupAgent to deploy it on a VM (requires to have a VM created and modify code to enter user's password at the moment).

• Small changes to existing PowerShell helpers to custom PS function work (add useLocalScope parameter).

Validation steps performed

Ran new test, verified that binaries were deployed on the target VM.
Manual debugging of C# and PS code.

PR checklist

• Closes #xxx
• Tests added/passed
• Documentation updated

[bbonaby]

Its best practice to put the $null on the left side of the comparison for PowerShell:
https://learn.microsoft.com/en-us/powershell/scripting/learn/deep-dives/everything-about-null?view=powershell-7.2#checking-for-null , so I think we can update it here and also anywhere below.

Suggested change

	if ($service -ne $null)
	if ($null -ne $service)

[sshilov7]

Seems like it should be just "if ($service)".

[bbonaby]

I think Eric was saying something about cred scan in the pipelines not liking the use of even test usernames and passwords. So just in case we should probably do it like this, to obfuscate it a little more:

Suggested change

	var userName = "LocalAdmin";
	var pwd = new NetworkCredential(string.Empty, "<>").SecurePassword;
	deploymentHelperMock.Object.DeployDevSetupAgent(userName, pwd);
	deploymentHelperMock.Object.DeployDevSetupAgent("LocalAdmin", new NetworkCredential(string.Empty, "<>").SecurePassword);

[sshilov7]

How does it obfuscate it? Or do you know how that detection works? Those values don't matter as you have to change them into real ones. I can just use string.empty.

[bbonaby]

I was thinking more that the cred scan would be looking for variable names like "username" and "pwd" within a function.

[bbonaby]

oh interesting I had assumed a user could pause any service if they had permission.