Deploying Azure IaaS Node fails executing Handler.cmd

#### Problem Description
When deploying an Azure IaaS node from HPC 2019, that is using a custom image and is not domain joined, deployment fails after an hour with "Provisioning of VM extension configHpcNonDomainCN has timed out"

#### Steps to Reproduce
1. Create a custom image
2. Create a node template that targets the custom image
3. Add Azure IaaS VM nodes
4. Start the newly created Azure Nodes

#### Expected Results
Azure node should deploy

#### Actual Results
The operation times out and fails due to errors during execution
#### Additional Logs

#### Additonal Comments
When looking into the deployment logs I can see the following error in "C:\WindowsAzure\Logs\Plugins\Microsoft.HpcPack.HPCComputeNode\2.0.7214.0\CommandExecution.log":
```
Execution Output:
C:\Packages\Plugins\Microsoft.HpcPack.HPCComputeNode\2.0.7214.0>Powershell.exe -NoProfile -NonInteractive -ExecutionPolicy Bypass -File C:\Packages\Plugins\Microsoft.HpcPack.HPCComputeNode\2.0.7214.0\\HpcExtensionHandler.ps1 -Action -Action

Execution Error:
C:\Packages\Plugins\Microsoft.HpcPack.HPCComputeNode\2.0.7214.0\HpcExtensionHandler.ps1 : Missing an argument for
parameter 'Action'. Specify a parameter of type 'System.String' and try again.
+ CategoryInfo : InvalidArgument: (:) [HpcExtensionHandler.ps1], ParentContainsErrorRecordException
+ FullyQualifiedErrorId : MissingArgument,HpcExtensionHandler.ps1
```

This error occurs after exeucting this: `C:\Packages\Plugins\Microsoft.HpcPack.HPCComputeNode\2.0.7214.0\Handler.cmd -Action reset`

The handler.cmd file contains the following:
`Powershell.exe -NoProfile -NonInteractive -ExecutionPolicy Bypass -File %~dp0\HpcExtensionHandler.ps1 -Action %1`

The deployment appears to execute Handler.cmd with incorrect parameters. I believe it should be sending 'handler.cmd reset' and not 'handler.cmd -action reset' because the action parameter is already set within the handler.cmd file.