Also accept cached (fromCache) responses in WASM caching check

The WASM caching enforcement check previously only accepted HTTP 304
(Not Modified) as proof that a .wasm resource was cached. However,
browsers may serve cached resources with HTTP 200 from disk/memory
cache without making a network round-trip at all. Puppeteer exposes
this via response.fromCache(). Both cases indicate the resource was
properly cached after the first page load, so both should be accepted.

Without this fix, the 'Second page load' step fails with:
  Unexpected uncached wasm resource '...System.Runtime.InteropServices.JavaScript.*.wasm'
even though the resource is served from the browser cache.

Co-authored-by: Copilot <[email protected]>

Author: ilonatommy

src/BenchmarksApps/Lighthouse/src/blazor-scenario.js

@@ -132,7 +132,8 @@ function throwOnFutureUncachedWasmDownloads(page) {
 
   page.on('requestfinished', request => {
     const url = request.url();
-    if (url.endsWith('.wasm') && request.response().status() !== 304) {
+    const response = request.response();
+    if (url.endsWith('.wasm') && response.status() !== 304 && !response.fromCache()) {
       throw new Error(`Unexpected uncached wasm resource '${url}'`);
     }
   });