fix: resolve cmd.exe quoting and stdin issues in Invoke-MaskedProcess

[petehauge]

Summary

Fixes two Windows-specific bugs in Invoke-MaskedProcess (LogMasking.psm1) that caused integration test failures when the deploy scripts run az commands inside Start-Job.

Changes

1. Stdin redirect hang fix

RedirectStandardInput was $false, so child processes spawned inside Start-Job (which has no parent console) inherited a broken stdin handle. Python (the az CLI runtime) hung on startup waiting for stdin initialization.

Fix: Set RedirectStandardInput = $true and close stdin immediately after Start().

2. cmd.exe /c argument quoting fix

ArgumentList individually quotes each argument using C-runtime conventions, but cmd.exe /c has its own incompatible quoting rules:

• Paths with spaces (C:\Program Files\...) broke because cmd.exe stripped individual quotes and split at the space → 'C:\Program' is not recognized
• Metacharacters like parentheses in JMESPath queries (e.g., length(value[?name=='...'])) were interpreted as cmd.exe grouping operators → --output was unexpected at this time.

Fix: For the cmd.exe /c case, use the Arguments string property instead of ArgumentList, with each argument individually quoted inside an outer /c "..." wrapper. This ensures cmd.exe passes all content through as literals.

Testing

• Verified az account show works inside Start-Job (previously hung indefinitely)
• Verified arguments with spaces and parentheses pass through correctly
• Full roundtrip integration test passes through publish phase