[ZH] Make Zero Hour Tools compile with VS2022 c++20

[xezon]

Merge with Rebase

• Relates to Get Generals and Zero Hour to compile with vs2022 & c++20 #471
• Follow up for [ZH] Make Zero Hour game compile with VS2022 c++20 #426

---

This change makes Zero Hour Tools build with VS2022 and c++20. It still builds all targets with VS6 and is not expected to change behaviour.

Compile & Linker warnings are not addressed with this change.

---

(GENZH_BUILD_ZEROHOUR ✔️)
GENZH_BUILD_ZEROHOUR_TOOLS ✔️
(GENZH_BUILD_GENERALS ✔️)
GENZH_BUILD_GENERALS_TOOLS ❌

Zero Hour & Tools build on VS6 ✔️
Zero Hour & Tools build on VS2022 c++20 ✔️
(Generals build on VS6 ✔️)
(Generals build on VS2022 c++20 ✔️)

---

Commits are split into small chunks for ease of review.

[Mauller]

Looks fine to me overall, some of the things are inconsequential in the end as the tools they are in are likely to end up deprecated in the long run.

[OmniBlade]

Missed a trick when I approved earlier, didn't test the new extras build. The following libraries need gz_config adding to their targets so they correctly use C++20:

CRCDiff
Launcher
mangler
matchbot
timingTest

[xezon]

CRCDiff
Launcher
mangler
matchbot
timingTest

Why just these 5? I have now added gz_config to the following targets:

z_compression
z_assetcull
z_autorun
z_babylon
z_buildversionupdate
z_compress
z_crcdiff
z_debugwindow
z_launcher
z_datgen
z_manglerlib
z_matchbot
z_particleeditor
z_texturecompress
z_timingtest
z_versionupdate
z_wolsetup

This appears to be complete. Is that ok?

[OmniBlade]

Those were just the ones that needed to be C++17 or higher to build correctly based on something in one of compatibility wrappers you wrote, but all targets being bumped is also a perfectly good fix.

[xezon]

Pull number needs to be added to commits.