🐛 powershell: write stderr read error to the stderr field

[tas50]

Bug

In powershell.go, the branch that handles a failed io.ReadAll(x.Stderr) assigned the error to c.Stdout instead of c.Stderr:

stderr, err := io.ReadAll(x.Stderr)
if err != nil {
    c.Stdout = plugin.TValue[string]{Error: err, State: plugin.StateIsSet}  // wrong field
} else {
    ...
    c.Stderr = plugin.TValue[string]{...}
}

This is a copy-paste slip from the stdout block above it. When reading stderr fails, it clobbers the stdout value that was just populated correctly and leaves c.Stderr in its zero/unset state — so powershell { stdout, stderr } reports a bogus error on .stdout while .stderr is silently never set.

The powershell resource underlies auditpol and secpol, so those inherit the corruption on this error path.

Fix

Assign the stderr read error to c.Stderr.

🤖 Generated with Claude Code

https://claude.ai/code/session_015U1ocAxfcBhVYi3f9JnyZZ

---

Generated by Claude Code

[github-actions]

All contributors have signed the CLA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

[mondoo-code-review]

Fixes PowerShell stderr read errors being incorrectly reported on the stdout field instead of stderr.

[github-actions]

Test Results

11 153 tests  ±0   11 146 ✅ ±0   3m 24s ⏱️ - 1m 56s
   545 suites ±0        7 💤 ±0 
    40 files   ±0        0 ❌ ±0 

Results for commit 8ccea2a. ± Comparison against base commit a92a575.

♻️ This comment has been updated with latest results.