[wasm-simd] Use no_simd_sse to skip test instead of forcing flags

Bug: v8:10773
Change-Id: I2f2a828bea66c7547d988c6f4c36cbd48c7f85b0
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2842384
Commit-Queue: Zhi An Ng <zhin@chromium.org>
Reviewed-by: Deepti Gandluri <gdeepti@chromium.org>
Cr-Commit-Position: refs/heads/master@{#74109}

test/message/message.status

@@ -79,4 +79,10 @@
   # Tests that require Simd enabled.
   'wasm-trace-memory': [SKIP],
 }],
+
+##############################################################################
+['no_simd_sse == True', {
+  'wasm-trace-memory': [SKIP],
+  'wasm-trace-memory-liftoff': [SKIP],
+}],  # no_simd_sse == True
 ]

test/message/wasm-trace-memory-liftoff.js

@@ -4,7 +4,6 @@
 
 // Flags: --no-stress-opt --trace-wasm-memory --liftoff
 // Flags: --no-wasm-tier-up --experimental-wasm-simd
-// Flags: --enable-sse3 --enable-sse4-1
 
 // Force enable sse3 and sse4-1, since that will determine which execution tier
 // we use, and thus the expected output message will differ.

test/message/wasm-trace-memory.js

@@ -4,7 +4,6 @@
 
 // Flags: --no-stress-opt --trace-wasm-memory --no-liftoff
 // Flags: --experimental-wasm-simd
-// Flags: --enable-sse3 --enable-sse4-1
 
 load("test/mjsunit/wasm/wasm-module-builder.js");