Add static library and x64 build configurations.

Also introducing a naming scheme for all the different build permutations
while we're at it.

...

So, I've put myself through the lovely joy of optimizing Visual Studio
projects once again. I didn't get to rant about it last time or the time
before, so...

External build systems are generally horrible, but MSBuild has to one of the
worst to ever exist. The order of statements inside the .vcxproj actually
*matters*, some parts of Visual Studio only parse certain tags, certain other
tags that seemingly do nothing are actually mandatory... and the slightest
failure to comply to these unwritten (?) rules usually breaks your build in
weird ways, all of that constantly reminding you what a fool you are to
actually try and optimize these by hand.

Yeah, why would you *possibly* want to go away from these unwieldy compilation
setting menus and condense these settings to something you can actually edit
and verify comfortably in a plaintext editor?

Like, do you see that empty <PropertyGroup Label="UserMacros" /> tag in there?
Removing that somehow leads to the standard C library include paths no longer
being available, which in turn single-handedly destroys IntelliSense. For some
reason, the program still builds, though?!?

In the end, even if some tags in the .vcxproj may still look redundant, you
can be sure that I meticulously tested removing, simplifying and reordering
*everything* in there. This *is* the most optimal and least redundant build
setup you can possibly get.

...

But y'know, although was annoying to get there, I still prefer it over CMake
vomiting all that *stuff* into my build tree.