Use UTF-8 for MSVC and enable visual styles for Windows

[xoascf]

• Adds a Windows application manifest that provides specific information about supported OS versions and enables visual styles
• Uses the UTF-8 encoding compilation option to allow the project to compile on Windows regardless of the language for non-Unicode programs (this fixes compilation if you have this setting in Japanese and other languages)

Build Artifacts

• soh.otr.zip
• soh-linux-compatibility.zip
• soh-linux-performance.zip
• soh-mac.zip
• soh-switch.zip
• soh-windows.zip

[leggettc18]

As it is, not opposed to this making it in, but I have a few questions. Some of them were left as code comments, and one is below:

Is there some tangible affect of the manifest that I would actually be able to see? If it's just that having a manifest is a correctness thing that's fine, just curious if I could actually do something with this to verify that it's working.

[xoascf]

Is there some tangible affect of the manifest that I would actually be able to see? If it's just that having a manifest is a correctness thing that's fine, just curious if I could actually do something with this to verify that it's working.

Yep, you can see the difference when running the ROM extraction process.

Before:

With this PR:

[leggettc18]

Perfect, the difference on Windows 11 for reference. Left is Spock Bravo, right is this PR: