fix: preserve non-ASCII characters in CSV output

[1junh]

Summary

When a certificate template name contains non-ASCII characters (e.g. Japanese), Invoke-Locksmith writes them as ? in its CSV output. The affected files are *ADCSIssues.CSV (Mode 2) and *ADCSRemediation.CSV (Mode 3).

Example (Mode 2), template name 脆弱テンプレートESC1:

Before: "yamato.local","ESC1","????????ESC1", ...
After:  "yamato.local","ESC1","脆弱テンプレートESC1", ...

Root cause

The two Export-Csv calls don't specify -Encoding, so they fall back to the cmdlet's default — and that default differs by PowerShell version.

References:

• Windows PowerShell 5.1 — Default value: ASCII
  https://learn.microsoft.com/powershell/module/microsoft.powershell.utility/export-csv?view=powershell-5.1
• PowerShell 7.6 — Default value: UTF8NoBOM
  https://learn.microsoft.com/powershell/module/microsoft.powershell.utility/export-csv?view=powershell-7.6

Fix

Add -Encoding UTF8 to the two Export-Csv calls in Public/Invoke-Locksmith.ps1. UTF8 is a valid value on both Windows PowerShell 5.1 and PowerShell 7+.

Testing

Ran Invoke-Locksmith -Mode 2 -OutputPath . on Windows PowerShell 5.1 against a forest containing a template whose name includes Japanese characters. Before the change the name was written as ?; after the change the CSV preserves the characters correctly.