deps: V8: backport 85b390089e51

Original commit message:

    [wasm][eh] Fix getArg() when exception has an S128

    We cannot read an S128 exception value from JS, but we can read a value
    at a higher index in the exception. So accept S128 values when we
    compute the encoded index.

    R=mliedtke@chromium.org

    Fixed: 403675482
    Change-Id: I7cc0238310863b6d579fcbe0a216ddce6f760c8b
    Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6367014
    Reviewed-by: Matthias Liedtke <mliedtke@chromium.org>
    Commit-Queue: Thibaud Michaud <thibaudm@chromium.org>
    Cr-Commit-Position: refs/heads/main@{#99305}

Refs: v8/v8@85b390089e51

Author: thibaudmichaud

common.gypi

@@ -38,7 +38,7 @@
 
     # Reset this number to 0 on major V8 upgrades.
     # Increment by one for each non-official patch applied to deps/v8.
-    'v8_embedder_string': '-node.55',
+    'v8_embedder_string': '-node.56',
 
     ##### V8 defaults for Node.js #####
 

deps/v8/src/wasm/wasm-js.cc

@@ -2754,12 +2754,14 @@ void WebAssemblyExceptionGetArgImpl(
       case i::wasm::kRefNull:
         decode_index++;
         break;
+      case i::wasm::kS128:
+        decode_index += 8;
+        break;
       case i::wasm::kRtt:
       case i::wasm::kI8:
       case i::wasm::kI16:
       case i::wasm::kVoid:
       case i::wasm::kBottom:
-      case i::wasm::kS128:
         UNREACHABLE();
     }
   }