[wasm] Update spec tests

Some tests are failing now and have been marked as failing to
investigate them.

R=jkummerow@chromium.org

Change-Id: I1242ccf3bdc8f4d2ff55bc016c43fa51c556376e
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2366696Reviewed-by: Jakob Kummerow <jkummerow@chromium.org>
Commit-Queue: Andreas Haas <ahaas@chromium.org>
Cr-Commit-Position: refs/heads/master@{#69513}

test/wasm-js/tests.tar.gz.sha1

-3bc1c30d8286fef436d08e5cbe5508ddb4e69ad6
\ No newline at end of file
+e17c5119c343be682a2783156c4a56c2528333a3
\ No newline at end of file

test/wasm-spec-tests/tests.tar.gz.sha1

-342913732440647d224359974191e907f810123f
\ No newline at end of file
+10a6b24d01b5124f14658e7a4b8c354138d62386
\ No newline at end of file

test/wasm-spec-tests/wasm-spec-tests.status

@@ -5,6 +5,10 @@
 [
 [ALWAYS, {
   'skip-stack-guard-page': [PASS, ['((arch == ppc or arch == ppc64 or arch == s390 or arch == s390x) and simulator_run)', SKIP]],
+  # TODO(wasm) Investigate failing spec tests after update.
+  'binary': [FAIL],
+  'proposals/js-types/binary-leb128': [FAIL],
+  'proposals/bulk-memory-operations/binary-leb128': [FAIL],
 
   # TODO(v8:9144): The MVP behavior when bounds-checking segments changed in
   # the bulk-memory proposal. Since we've enabled bulk-memory by default, we