Fixes internal VSO-2431296, where P2321R2_views_adjacent is sporadically running out of memory for x86-native /analyze:only configurations. (Internal builds of the compiler have a bit more debug logic than retail builds, which is why we haven't seen these failures in our GitHub PR/CI system.)

Related:

• <algorithm>: /analyze with ranges algorithms emits fatal error C1060: compiler is out of heap space #1030
• Ranges tests consuming excessive compiler memory #3567

Our stressful ranges/views tests, combined with Static Analysis's increased compiler memory consumption, interact poorly with the ABSOLUTE ABOMINATION of x86-hosted toolsets in the year 2025.

I modified #3567's incantations to find all of the tests that were consuming 3+ GB for x86-native /analyze:only, then added our usual workarounds, reducing the peak working set sizes (in bytes) to reasonable levels:

As usual, the workarounds are architecture-independent, since consuming tons of memory isn't great even for properly x64-hosted compilers.

I also checked the plain configurations (original recipe C1XX, not extra crispy /analyze:only). There are only a few at 2+ GB for x86-native, and none over 3 GB, so while they're still concerning, they aren't risking OOM:

(Note that /analyze:only is just a variant of /analyze that skips codegen.)