Fix parameter forwarding for pwsh
When using the pwsh script shell and trying to pass arguments after the double dash -- to an underlying PowerShell script, it did not like having the arguments escaped. Instead, in the pwsh case, specifically, we just concatenate the arguments to pass to the underlying command.
Note that instead of modifying the existing branch for non-cmd shells in CommandRunner.cs, I added a specific check for pwsh to ensure this change does not affect other shells like bash/sh.
See issue #398 for more context and a repro of the bug.
Hey @xt0rted! I'm eager to get this change merged and a new version published. Is there anything I can help with to get the process moving forward? Let me know if you have questions or concerns with this change. Thank you!
Hey @xt0rted! When do you think you'll have a chance to review and get this one merged? Would we be able to do a release after it's in? Thanks!