fix(powershell): don't use Invoke-Expression if ExpectingInput

[alexsch01]

dang, my apologies for getting this out after the npm release

this prevents a performance/security regression with piping strings into npm/npx

This should block nodejs/node#58347

---

echo "Hello" | npm help a=1,b=2,c=3

No matches in help for: a=1 b=2 c=3

---

npm help a=1,b=2,c=3

No matches in help for: a=1,b=2,c=3

---

This is the best compromise between convenience and security

[alexsch01]

Would be great to make it into 11.4.1
@owlstronaut @wraithgar

[alexsch01]

I was going to add a warning for the $ExpectingInput case when the $args variable contains an array as an element
but it doesn't cover the case of echo hello | npm start -- --arg1 --arg2, so I removed the warning

[alexsch01]

Converting to a draft because it's missing some features