fix: Windows compatibility for UTF-8 output and Rich console

[JohnFiedler]

Summary

• Add UTF-8 stream wrappers (io.TextIOWrapper) for sys.stdout/sys.stderr on Windows to handle emojis and special characters in scan output
• Use Console(force_terminal=True) for Rich console instances to ensure correct rendering on Windows terminals
• Always regenerate scan artifacts (not just when DAST is enabled), fixing securevibes report output on all platforms
• Add test for list-of-dicts evidence format

Files changed

• packages/core/securevibes/cli/main.py — UTF-8 wrapper + force_terminal
• packages/core/securevibes/scanner/scanner.py — UTF-8 wrapper + force_terminal + always regenerate artifacts + conditional debug message
• packages/core/securevibes/scanner/subagent_manager.py — UTF-8 wrapper + force_terminal
• packages/core/tests/test_scan_output.py — Test for evidence as list of dicts

Test plan

• Run securevibes scan on Windows and verify emoji/special characters render correctly
• Run securevibes report after a scan and verify artifacts are generated
• Run existing test suite: pytest packages/core/tests/

🤖 Generated with Claude Code

[anshumanbh]

@JohnFiedler Thank you for the PR. I pushed a bunch of changes introducing a new "pr-review" command. As a result of that, this PR has some conflicts. Do you mind taking a look at them and resolving them before I can review?