Setting RuntimeAsync=1 broke wasm

[jkotas]

This PR breaks browser/interp probably until we remove the temporary signature detection

To unblock us, we will turn asyncv2 for browser off in #122495
That PR also brings first CI smoke test for CoreCLR/WASM😅

Originally posted by @pavelsavara in #121732 (comment)

[dotnet-policy-service]

Tagging subscribers to this area: @mangod9
See info in area-owners.md if you want to be subscribed.

[jkotas]

The temporary signature detection should work just fine with RuntimeAsync=1. I think this suggests that there is a bug exposed by setting RuntimeAsync=1. Wasm just got unlucky to hit this bug first. We are likely going to see the underlying bug on other architectures in different scenarios.

[jkotas]

cc @VSadov @agocke