This includes Carbon support

This more closely matches the behaviour of CMake when adding rc files to
targets.

This also fixes an issue where the requested font style could be
incorrectly overwritten.

applicationId

This change allows users to use macro values defined by Visual Studio in
library names, which might be useful e.g. when selecting different
libraries based on the build configuration.

If the filename of a library contains a special character that would
have a special meaning in the Visual Studio project file, you must use
the ASCII escape sequence for this character instead ("$" becomes "%24",
"%" becomes "%25").

This escaping will happen automatically for non-user-specified library
dependencies, including windows libraries specified in module header
blocks, and the plugin shared code target.

This reverts commit 8bacf8c15c.

This reverts commit a71bda9adb.

This ensures that solution files have correctly numbered icons in
Windows Explorer.

By default, x86_64 binaries are not signed, but arm64 binaries are. When
building universal binaries, it was possible to end up with a final
artefact that contains an unsigned x86_64 image, but a signed arm64
image. In some cases, this could cause issues in subsequent codesign
invocations.

When the result of find_if() is only compared to the container's end(),
the operation can normally be expressed more concisely using any_of(),
all_of(), or none_of().

5f7ad995af introduced an issue where the
string of external libraries would be escaped in one go. This is
incorrect, because only the individual paths should be escaped. The
semicolons separating each path should not be escaped.

Without the BOM, VS assumes UTF-8 strings (subproject file names etc.)
are ansi-encoded.