Microsoft broke windows32 env variable setting

[mratsim]

No description provided.

[mratsim]

The last bug left in win32 seems to come from mingw undefined reference: Alexpux/mingw-w64#2

https://dev.azure.com/numforge/Weave/_build/results?buildId=340&view=logs&j=1dc2135d-7f2f-5e04-2f1c-000f370e57c5&t=3806340f-fc14-550d-444d-a3485218203e&l=171

C:\Users\VssAdministrator\nimcache\memory_pools_r\@mmemory_pools.nim.c.o:@mmemory_pools.nim.c:(.text+0x341c): undefined reference to `EnterSynchronizationBarrier@8'
C:\Users\VssAdministrator\nimcache\memory_pools_r\@mmemory_pools.nim.c.o:@mmemory_pools.nim.c:(.text+0x418a): undefined reference to `InitializeSynchronizationBarrier@12'
C:\Users\VssAdministrator\nimcache\memory_pools_r\@mmemory_pools.nim.c.o:@mmemory_pools.nim.c:(.text+0x420a): undefined reference to `InitializeSynchronizationBarrier@12'
collect2.exe: error: ld returned 1 exit status

Note sure why it wasn't triggered previously

[mratsim]

It's probable that either the previous or the current mingw-w64 setup between the builtin mingw in Azure and the one downloaded was wrong. Given that 87013fc commit was needed, I think the previous setup was not really using 32-bit test.

For now comment out Win 32-bit