fix(powershell): improve argument parsing

[alexsch01]

improve the argument parsing PS1 logic

• support & npm args and . npm args properly
• support syntax such as C:\"Program Files"\nodejs\npm.ps1 args

of course ^ for both npm and npx version of the script

Code Explanation: instead of getting the CommandElements.Extent.Text array and joining it with spaces right away, now it's getting the same array and only capturing everything after the first element

---

@wraithgar @mbtools sorry about this right after the other PR

[alexsch01]

OK PR is ready now

[mbtools]

C:\"Program Files"\nodejs\npm.ps1 is crappy style. "C:\Program Files\nodejs\npm.ps1" is the way to do it. But if it's valid, fine.

We're getting more cases that aren't covered by tests. However, the Windows Shims Test is already taking over 7 min. It loops over 7 shells (times 6 tests). Either the test itself needs a performance improvement, or we should have a separate test just for PowerShell that covers the recently added cases.

[alexsch01]

C:\"Program Files"\nodejs\npm.ps1 is crappy style. "C:\Program Files\nodejs\npm.ps1" is the way to do it. But if it's valid, fine.

The first one is required if you don't want to include the call (&) operator

It's also better code in this PR since we used to assume InvocationName was always in the command and that isn't true

[mbtools]

looks good

[alexsch01]

Made a minor variable name change
Hope this can make it into 11.5.3