[NativeAOT LLVM] Enable JS interop

[maraf]

• The goal is not to enable all JS import/export scenarios, but start with some simple ones
• Updated smoke tests
• The mono_wasm_bind_js_function and mono_wasm_bind_cs_function are duplicated for NativeAOT case
• Due to DisableImplicitFrameworkReferences=true in tests, generators are added as explicit references

Contributes to https://github.com/dotnet/runtimelab/issues/2434

[elringus]

@maraf Sorry if I'm asking something irrelevant here, but do I understand correctly that there are plans to move WASM target from Mono to NativeAOT/LLVM? If that's the case, will the existing "high-level" JS interop API (the JSImport/Export stuff from System.Runtime.InteropServices.JavaScript) still work with the new backend or it'll be something different?

[maraf]

@maraf Sorry if I'm asking something irrelevant here, but do I understand correctly that there are plans to move WASM target from Mono to NativeAOT/LLVM?

There is no such plan at the moment. Anyway NativeAOT/LLVM has come a long way and we are looking at comparison

If that's the case, will the existing "high-level" JS interop API (the JSImport/Export stuff from System.Runtime.InteropServices.JavaScript) still work with the new backend or it'll be something different?

The goal of the https://github.com/dotnet/runtimelab/issues/2434 is to have the same/close as possible API for both Mono and NativeAOT/LLVM in the context of the browser, so that is possible try to wasmbrowser based apps on NativeAOT/LLVM.