[test] Disable wasm-js/limits for sanitizers

The test is slow and checks the limits of the WebAssembly
implementation. Sanitizers are slower and therefore sometimes run into
timeouts. Therefore we just disable the test for sanitizers.

R=leszeks@chromium.org

Change-Id: I4a0cb994dfc34097849f0dd8528dc158883fbc8a
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2389980
Commit-Queue: Leszek Swirski <leszeks@chromium.org>
Reviewed-by: Leszek Swirski <leszeks@chromium.org>
Cr-Commit-Position: refs/heads/master@{#69667}

test/wasm-js/wasm-js.status

@@ -35,11 +35,11 @@
   'constructor/instantiate': [SKIP],
 }],  # 'arch == s390 or arch == s390x or system == aix'
 
-['mode == debug or simulator_run or variant != default or arch == arm', {
+['mode == debug or simulator_run or variant != default or arch == arm or tsan or msan or asan', {
   # Slow, and we always have the same limits anyway.
   # ODroid bots don't have enough memory to run the test.
   'limits': [SKIP],
-}],  # mode == debug or simulator_run or variant != default or arch == arm
+}],  # mode == debug or simulator_run or variant != default or arch == arm or tsan or msan or asan
 
 ##############################################################################
 ['lite_mode or variant == jitless', {