Quote dash-prefixed path arguments in PowerShell wrapper

[caomengxuan666]

Fixes one argument-passing edge case from #23.

In the PowerShell wrapper, bare arguments like -dash.txt are currently passed through unchanged. For .cmd targets running in Legacy native argument mode, PowerShell can split that token as -dash and .txt.

This change quotes extension-like dash-prefixed bare tokens before handing them to the .cmd entry point, while leaving ordinary bare globs unquoted so coreutils can still expand them.

Validated locally with the generated wrapper form:

cat -- '"-dash.txt"'
grep foo -- '"-dash.txt"'
cp -- '"-dash.txt"' dash-copy.txt

All three commands succeeded against a file named -dash.txt.

[IDisposable]

This regex will match -., -a., and -.a, if that isn't desired, should we use:

• ^-[^-](?!\.$)[^\s]*\.[^\s]*$ which will not match -.
• ^-[^-][^\s]+\.[^\s]+$ which requires something on both sides -a.b

[lhecker]

This PR is excellent, but I hesitate to merge it for a similar reason: I find it hard to reason about why PowerShell fails this way and how we can fix it in the most robust manner.

[caomengxuan666]

This regex will match -., -a., and -.a, if that isn't desired, should we use:

• ^-[^-](?!\.$)[^\s]*\.[^\s]*$ which will not match -.
• ^-[^-][^\s]+\.[^\s]+$ which requires something on both sides -a.b

Your concern is right,this regex is too loose.I will improve it

[caomengxuan666]

This PR is excellent, but I hesitate to merge it for a similar reason: I find it hard to reason about why PowerShell fails this way and how we can fix it in the most robust manner.

Yeah, we need to find out the reason first. An end-to-end test would help ensure correctness, but I agree that we need a deeper understanding of why PowerShell splits these tokens before we can design a robust fix. I'll investigate further.