[wasm] Reenable shared memory test

This reenables a test which is passing, independent of missing
accounting for shared memory. This is because we repeatedly trigger a GC
explicitly in all workers.

R=dinfuehr@chromium.org

Bug: v8:12278
Change-Id: I73d1513d809787284af0be4956018806719acd50
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3201995Reviewed-by: Dominik Inführ <dinfuehr@chromium.org>
Commit-Queue: Clemens Backes <clemensb@chromium.org>
Cr-Commit-Position: refs/heads/main@{#77219}

test/mjsunit/wasm/shared-memory-worker-explicit-gc-stress.js

@@ -6,8 +6,6 @@
 
 d8.file.execute("test/mjsunit/worker-ping-test.js");
 
-let kDisabledAbort = false; // TODO(9380): enable abort for this test
-
 let config = {
   numThings: 4,       // size of circular buffer
   numWorkers: 4,      // number of workers
@@ -16,7 +14,7 @@ let config = {
   traceScript: false, // print the script
   traceAlloc: true,   // print each allocation attempt
   traceIteration: 10, // print diagnostics every so many iterations
-  abortOnFail: kDisabledAbort,  // kill worker if allocation fails
+  abortOnFail: true,  // kill worker if allocation fails
 
   AllocThing: function AllocThing(id) {
     let pages = 1, max = 1;