[wasm][aot] Don't AOT the helper assemblies for `ApplyUpdateTest.StaticMethodBodyUpdate` in `System.Runtime.Loader` tests

[radical]

AOT tracking PR has:

[17:48:49] fail: [FAIL] System.Reflection.Metadata.ApplyUpdateTest.StaticMethodBodyUpdate
[17:48:49] info: Assert.Equal() Failure
[17:48:49] info:           ↓ (pos 0)
[17:48:49] info: Expected: NEW STRING
[17:48:49] info: Actual:   OLD STRING
[17:48:49] info:           ↑ (pos 0)

According to @lambdageek we shouldn't be AOT'ing the assemblies being used by the ApplyUpdateTests(eg. https://github.com/dotnet/runtime/blob/main/src/libraries/System.Runtime.Loader/tests/System.Runtime.Loader.Tests.csproj#L41)

We would need to set %(WasmASsembliesToBundle._InternalForceInterpret)=true for such assemblies.

Also, would be nice to have a common way of doing this across wasm/iOS/android.

Note: this doesn't fail on main because System.Runtime.Loader.Tests are disabled completely

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

---

AOT tracking PR has:

[17:48:49] fail: [FAIL] System.Reflection.Metadata.ApplyUpdateTest.StaticMethodBodyUpdate
[17:48:49] info: Assert.Equal() Failure
[17:48:49] info:           ↓ (pos 0)
[17:48:49] info: Expected: NEW STRING
[17:48:49] info: Actual:   OLD STRING
[17:48:49] info:           ↑ (pos 0)

According to @lambdageek we shouldn't be AOT'ing the assemblies being used by the ApplyUpdateTests(eg. https://github.com/dotnet/runtime/blob/main/src/libraries/System.Runtime.Loader/tests/System.Runtime.Loader.Tests.csproj#L41)

We would need to set %(WasmASsembliesToBundle._InternalForceInterpret)=true for such assemblies.

Also, would be nice to have a common way of doing this across wasm/iOS/android.

Author:	radical
Assignees:	-
Labels:	arch-wasm
Milestone:	-

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

[lewing]

Is there any reason to run this test when AOTing? Do we have any plan to do hot reload in combination with AOT?

[lambdageek]

Is there any reason to run this test when AOTing? Do we have any plan to do hot reload in combination with AOT?

@lewing yes - we should eventually support a hybrid execution mode where the BCL is AOTd but the user assemblies are interpreted and are hot-reloadable. In principle the runtime can already support it. (Maybe just on mobile, though)

[lewing]

This was more a question of "Are we officially supporting hot-reload on Wasm with aot+interp on .NET6" than "does it work" (it does).

cc @marek-safar

[marek-safar]

I don't think we need hybrid or full AOT support for webassembly hot reload. We could even block it with some error message to make it clear that something went wrong when settings things up.

[radical]

Closing in favor of #54617