Refactor MSVC project files

[DanRStevens]

Noticed a few things about the project files that could be improved:

• [x] We want warnings as errors on CI, but perhaps only on CI, not for local builds
• [x] There are some unused settings, such as pre-processor defines
• [x] We attempt to package on every build, rather than on demand, or on tagging of a version
• [x] We could be running Code Analysis
• [x] Build configuration sections are not always in a consistent order with new project files
• [x] Duplicated settings between configurations (there may be some MSVC IDE limitations on de-duplicating)
• [x] Build intermediate and output folders are inconsistent between platforms
• [x] We can probably use some vcpkg updates (#373), and perhaps switch to Manifests (https://github.com/OutpostUniverse/OPHD/issues/1374)

[DanRStevens]

Note that enabling Code Analysis currently shows errors in Google Test code. Considering we've disabled error reporting in external code (angle bracket #include <>), and we've used proper external includes for Google Test, this would seem to be a compiler error in reporting of those warnings.

Potentially we can disable those specific warnings for the test project using a <NOWARN> a property, as illustrated in the documentation: https://learn.microsoft.com/en-us/visualstudio/ide/how-to-suppress-compiler-warnings?view=vs-2022

<NoWarn>40059,42024</NoWarn>

Code Analysis can be enabled on the command line with msbuild by passing the argument /property:RunCodeAnalysis=true. Additionally, it seems there is a project file property set to enable Code Analysis, but currently only for the core NAS2D project (<RunCodeAnalysis>true</RunCodeAnalysis>).