UMF build fails on Windows 2022 with clang v18.1.8

[ldorau]

UMF build fails on Windows 2022 with clang v18.1.8 (x86_64-pc-windows-msvc):
https://github.com/ldorau/unified-memory-framework/actions/runs/13260441790/job/37015619453

MSBuild version 17.12.12+1cce77968 for .NET Framework

  1>Checking Build System
  Building Custom Rule D:/a/unified-memory-framework/unified-memory-framework/src/coarse/CMakeLists.txt
  coarse.vcxproj -> D:\a\unified-memory-framework\unified-memory-framework\build\lib\Release\coarse.lib
  Building Custom Rule D:/a/unified-memory-framework/unified-memory-framework/src/CMakeLists.txt
Warning: C:\Program Files\Microsoft Visual Studio\2022\Enterprise\VC\Tools\Llvm\x64\lib\clang\[18](https://github.com/ldorau/unified-memory-framework/actions/runs/13260441790/job/37015619453#step:10:19)\include\stddef.h(31): warning RC4067: unexpected characters following '#if/#elif' directive; newline expected [D:\a\unified-memory-framework\unified-memory-framework\build\src\umf.vcxproj]
  
Warning: C:\Program Files\Microsoft Visual Studio\[20](https://github.com/ldorau/unified-memory-framework/actions/runs/13260441790/job/37015619453#step:10:21)22\Enterprise\VC\Tools\Llvm\x64\lib\clang\18\include\stddef.h(31): warning RC4067: unexpected characters following '#if/#elif' directive; newline expected [D:\a\unified-memory-framework\unified-memory-framework\build\src\umf.vcxproj]
  
Error: C:\Program Files\Microsoft Visual Studio\20[22](https://github.com/ldorau/unified-memory-framework/actions/runs/13260441790/job/37015619453#step:10:23)\Enterprise\VC\Tools\Llvm\x64\lib\clang\18\include\__stddef_ptrdiff_t.h(15): fatal error RC1012: mismatched parenthesis : missing ' [D:\a\unified-memory-framework\unified-memory-framework\build\src\umf.vcxproj]

UMF build passes on Windows 2019 with the same clang v18.1.8 (x86_64-pc-windows-msvc):
https://github.com/ldorau/unified-memory-framework/actions/runs/13263489054/job/37025170478

Ref: #909
Ref: #1092

[ldorau]

Windows Clang CI job still does not work on windows-2022, but it works in CI on windows-2019, so it is not a high priority bug any more.