Route requests for missing static files using remote asset metadata - Second attempt

[brandonpayton]

Motivation for the change, related issues

Prior to this PR, we could not easily tell whether we should request a
missing static asset from the web or delegate a request for a missing file
to WordPress.

Related to #1365 where we need better information to judge whether to
handle a request for a missing static file as PHP.

Implementation details

This PR:

• Includes a list of remote asset paths with minified WP builds
• Updates request handling to only handle missing files as static when
  they are explicitly listed as remote assets
  (perhaps this should be split into multiple PRs)
• Updates request routing to behave more like a regular web server

By including a list of remote asset paths with minified WP builds, we
can judge which missing static file paths represent remote assets and
which are truly missing and need to be delegated to WordPress.

Testing Instructions (or ideally a Blueprint)

• CI tests
• Test manually with npm run dev and observe that Playground loads
  normally with no unexpected errors in the console

[brandonpayton]

Note: The e2e tests for this PR may fail until I push rebuilt versions of the minified WP zips.

[brandonpayton]

We are getting the following e2e failures which I am able to reproduce locally:

  2 failing                                                                                               
  1) Remote Assets                                                                                        
       should load remote assets for WordPress-6.3 and storage=browser:                             
     TypeError: Cannot set property message of [object DOMException] which has only a getter        
      at modifyErrMsg (http://localhost/__cypress/runner/cypress_runner.js:75124:15)                
      at $Cy.retry (http://localhost/__cypress/runner/cypress_runner.js:144185:29)                        
      at onFailFn (http://localhost/__cypress/runner/cypress_runner.js:143757:21)                         
      at tryCatcher (http://localhost/__cypress/runner/cypress_runner.js:1807:23)                   
      at Promise._settlePromiseFromHandler (http://localhost/__cypress/runner/cypress_runner.js:1519:31)
      at Promise._settlePromise (http://localhost/__cypress/runner/cypress_runner.js:1576:18)       
      at Promise._settlePromise0 (http://localhost/__cypress/runner/cypress_runner.js:1621:10)      
      at Promise._settlePromises (http://localhost/__cypress/runner/cypress_runner.js:1697:18)      
      at _drainQueueStep (http://localhost/__cypress/runner/cypress_runner.js:2407:12)              
      at _drainQueue (http://localhost/__cypress/runner/cypress_runner.js:2400:9)                   
      at Async._drainQueues (http://localhost/__cypress/runner/cypress_runner.js:2416:5)            
      at Async.drainQueues (http://localhost/__cypress/runner/cypress_runner.js:2286:14)            
                                                                                                          
  2) Remote Assets                                                                                        
       should load remote assets for WordPress-6.2 and storage=browser:                             
     TypeError: Cannot set property message of [object DOMException] which has only a getter        
      at modifyErrMsg (http://localhost/__cypress/runner/cypress_runner.js:75124:15)                
      at $Cy.retry (http://localhost/__cypress/runner/cypress_runner.js:144185:29)                        
      at onFailFn (http://localhost/__cypress/runner/cypress_runner.js:143757:21)                         
      at tryCatcher (http://localhost/__cypress/runner/cypress_runner.js:1807:23)                   
      at Promise._settlePromiseFromHandler (http://localhost/__cypress/runner/cypress_runner.js:1519:31)
      at Promise._settlePromise (http://localhost/__cypress/runner/cypress_runner.js:1576:18)       
      at Promise._settlePromise0 (http://localhost/__cypress/runner/cypress_runner.js:1621:10)      
      at Promise._settlePromises (http://localhost/__cypress/runner/cypress_runner.js:1697:18)      
      at _drainQueueStep (http://localhost/__cypress/runner/cypress_runner.js:2407:12)              
      at _drainQueue (http://localhost/__cypress/runner/cypress_runner.js:2400:9)                   
      at Async._drainQueues (http://localhost/__cypress/runner/cypress_runner.js:2416:5)            
      at Async.drainQueues (http://localhost/__cypress/runner/cypress_runner.js:2286:14)    

I'm not sure why this is only affecting WP 6.2 and 6.3 and why it is only erroring for storage=browser. In practice, both WP versions load and reload fine with storage=browser in my local environment.

[brandonpayton]

We are getting the following e2e failures which I am able to reproduce locally:

In local testing, the e2e failures didn't appear to have anything to do with WP 6.2 or 6.3 specifically. It seemed to have more to do with the quantity of tests, though I am not 100% on that.t also might have to do with not automatically clearing browser storage when the WP version changes in the URL.

For now, I reduced the tests to just testing storage=none and storage=browser for the default WP version.

[brandonpayton]

This is getting painful. I'm going to revert this because people with existing browser storage are going to have issues if /wordpress/wordpress-remote-asset-paths is not found. That was clear when this was originally reverted, but I focused on stopping the deletion of the listing file rather than considering browser storage prior to the existence of the listing.