fix(runner): whitelist Windows profile and temp vars in hermetic env

[dany-aspire]

Fixes #67385.

Problem

On native Windows, fails because strips , , , , , and variables, causing test collection crashes whenever tests touch or write temporary files. Consoles also fail when encoding tick glyphs.

Fix

• Appended conditional passthrough of , , , , , and in using syntax (ensuring macOS/Linux environments remain byte-identical).
• Added to force UTF-8 stdout encoding on Windows, resolving charmap encode errors.

[alt-glitch]

This was generated by AI during triage.

Related: #67387 already covers this environment passthrough and additionally supports the native Windows venv layout. This focused subset remains related rather than a duplicate so maintainers can choose the preferred scope.

[teknium1]

Thanks for isolating the Windows environment allowlist issue.

Problems

• scripts/run_tests.sh:46-53 only recognizes a POSIX venv (bin/activate, then bin/python). A standard native-Windows venv uses Scripts/activate and Scripts/python.exe, so the runner reaches the error at scripts/run_tests.sh:61-64 before the new env -i passthrough at this PR's added line 101 can execute. The member-linked #67387 already carries the required Scripts/ probe alongside the same allowlist change.

Suggested changes

• Include a guarded Scripts/activate / Scripts/python.exe venv path, then keep the proposed Windows environment passthrough and PYTHONUTF8=1 change.

Automated hermes-sweeper review.

[teknium1]

This allowlist is reached only after venv discovery. Current scripts/run_tests.sh:46-53 requires bin/activate and bin/python, so a standard native-Windows Scripts/activate venv exits at lines 61-64 before this line runs unless HERMES_PYTHON is supplied. Please add the guarded Scripts/ probe included by related #67387.

[dany-aspire]

Closing in favor of #67387, which implements the complete fix for #67385 (including the Windows Scripts/ venv probe this PR was missing). Thanks!