fuzzgen: fix generated code for MSVC/Windows
Three issues prevented the generated fuzz tests from compiling with MSVC:
1. FuzzData::nextInt<T> (template) and nextInt() (non-template) shared the
same name. Rename the template to nextRaw<T>() so explicit template calls
like fd.nextRaw<long>() are unambiguous on MSVC.
2. nextBool() returned (uint8_t & 1) as bool, triggering MSVC C4800. Use
an explicit (... != 0) comparison instead.
3. std::max in the generated main() could be shadowed by the min/max macros
from <windows.h>. Add a NOMINMAX guard at the top of all generated .cpp
files.
Also fix the ENABLE_ASAN cmake option to use /fsanitize=address on MSVC
instead of the GCC/Clang -fsanitize=address,undefined flags, and correct
Platform::MacOS/IOS enum name typos (should be macOS/iOS).
Change-Id: Idf74d406a8972528a1223ad9e2345ae655e9d9a7
Reviewed-by: Frederic Lefebvre <frederic.lefebvre@qt.io>