[blink] Re-enable wasm cache test

The streaming compilation top tier callback is now triggered, even
when the module is actually fetched from V8's in-memory module cache.

R=ahaas@chromium.org

Bug: v8:10165
Change-Id: I6f053c27c7ccf4d7ecae6fba709b48c08caf02fc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2037994Reviewed-by: Andreas Haas <ahaas@chromium.org>
Commit-Queue: Thibaud Michaud <thibaudm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#738523}

third_party/blink/web_tests/TestExpectations

@@ -6254,8 +6254,6 @@ crbug.com/1026712 [ Mac ] virtual/form-controls-refresh-disabled/fast/forms/time
 # The Wasm code cache requires disabling the baseline compiler, so only the
 # virtual test should be run.
 http/tests/devtools/wasm-isolated-code-cache/wasm-cache-test.js [ Skip ]
-# Temporarily disabled to land wasm module caching for streaming compilation in V8 (https://crbug.com/v8/10165).
-virtual/wasm-site-isolated-code-cache/http/tests/devtools/wasm-isolated-code-cache/wasm-cache-test.js [ Failure Pass ]
 
 # Memory measurement tests are run as virtual tests.
 external/wpt/measure-memory/measure-memory.tentative.any.html [ Skip ]