Only try OOM allocation size with 'absurd' value (#4489)

The current value version of the OOM allocation causes issues with
machines that have more than 128GB of RAM. Since one of the values it
tries to test is 128GB. This change removes this lower value, leaving
the higher value kMaxSafeMultipleOf8, which is ~8,192TB.

I am aware of no commercially available machine supports anything near
this much RAM, so this should be good for the foreseeable future. If
there is a device in the future with this much RAM, hopefully Number
will have been re-specified to something like a float128 by then.

Fixes #4488

Author: zoddicus

src/webgpu/api/operation/buffers/map_oom.spec.ts

@@ -10,12 +10,7 @@ import { kMaxSafeMultipleOf8 } from '../../../util/math.js';
 const oomAndSizeParams = kUnitCaseParamsBuilder
   .combine('oom', [false, true])
   .expand('size', ({ oom }) => {
-    return oom
-      ? [
-          kMaxSafeMultipleOf8,
-          0x20_0000_0000, // 128 GB
-        ]
-      : [16];
+    return oom ? [kMaxSafeMultipleOf8] : [16];
   });
 
 export const g = makeTestGroup(AllFeaturesMaxLimitsGPUTest);