Clarify encoding rationale for example PowerShell scripts

[Copilot]

Responded to question about why example PowerShell scripts use UTF-8/ASCII encoding with LF line endings instead of Windows-specific CRLF.

Context

The example scripts follow repository-wide .editorconfig standards (end_of_line = lf, charset = utf-8) for consistency. This encoding:

• Prevents cross-platform encoding issues
• Works natively on macOS/Linux
• Is fully compatible with PowerShell Core (6+) and Windows PowerShell 5.1

No code changes required—existing encoding is correct and cross-platform compatible.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}