Regression: Blazor InteractiveAuto doesn't work in browser without WebAssembly support after update to .NET 8.0.2

### Is there an existing issue for this?

- [X] I have searched the existing issues

### Describe the bug

@MackinnonBuck It looks there is a regression described by @Evengard in this comment https://github.com/dotnet/aspnetcore/issues/52154#issuecomment-1963153169.

I have just tested my very simple application which was published 2-3 months ago (.NET 8.0.0). It has a few pages rendered on the server (SSR) and a "counter" page configured as:
`@rendermode InteractiveAuto`
I don't know if it is important but server doesn't support web sockets - Blazor fallbacks to polling in server interactive mode.

Old version worked correctly in Firefox with javascript.options.wasm disabled. WASM files were not loaded and the application was running in server interactive mode. Then I enabled the javascript.options.wasm option and refreshed the page. The WASM files were loaded and the application worked in client interactive mode.

Currently (in .NET 8.0.2) "counter" page is prerendered on the server and displayed in the browser but browser displays this message in console:
Uncaught (in promise) Error: This browser does not support WebAssembly.

In my opinion for pages (or whole application) configured to work as `InteractiveAuto` you should use server interactive mode if WASM is not available.

You can go even further. Let's assume my WASM application is published with support for SIMD instructions (this is default configuration in 8.0). Unfortunately they are not available in iOS 15.x. You should test for SIMD support and fallback to SSI mode in case it is not supported. Related issue: https://github.com/dotnet/aspnetcore/issues/48756

### Expected Behavior

_No response_

### Steps To Reproduce

_No response_

### Exceptions (if any)

_No response_

### .NET Version

_No response_

### Anything else?

_No response_