Co-authored-by: Ankit Jain <radical@gmail.com>

.. instead crashing with an exception like:

```
src/mono/wasm/build/WasmApp.Native.targets(296,5): error MSB4018: (NETCORE_ENGINEERING_TELEMETRY=Build) The "ManagedToNativeGenerator" task failed unexpectedly.
System.BadImageFormatException: This PE image is not a managed executable.
   at System.Reflection.MetadataLoadContext.LoadFromStreamCore(Stream peStream)
   at System.Reflection.MetadataLoadContext.LoadFromAssemblyPath(String assemblyPath)
   at PInvokeTableGenerator.Generate(String[] pinvokeModules, String[] assemblies, String outputPath) in /_/src/tasks/WasmAppBuilder/PInvokeTableGenerator.cs:line 42
   at ManagedToNativeGenerator.ExecuteInternal() in /_/src/tasks/WasmAppBuilder/ManagedToNativeGenerator.cs:line 68
   at ManagedToNativeGenerator.Execute() in /_/src/tasks/WasmAppBuilder/ManagedToNativeGenerator.cs:line 53
   at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()
   at Microsoft.Build.BackEnd.TaskBuilder.ExecuteInstantiatedTask(ITaskExecutionHost taskExecutionHost, TaskLoggingContext taskLoggingContext, TaskHost taskHost, ItemBucket bucket, TaskExecutionMode howToExecuteTask)
```

The wasm targets currently are not able to differentiate the managed
assemblies from the unmanaged ones. so it needs to be handled here.

…leSIMD=true

Instead, let the property be effective only for the AOT case.

…move v8 config as that isn't supported

…runtime into pr-wasm-enable-simd

Also remove --experimental-wasm-simd option, which shouldn't be needed
for newer v8

As we need newer v8

The correlation payload is read only

This reverts commit a15b3ef.

Let see whether it will avoid all the writes to correlation payload
path

To try if we can use newer node in path

…e-simd

This reverts commit 5dec1aa.

The correlation payload is read only. And even with
`export DOTNET_SKIP_FIRST_TIME_EXPERIENCE=1` we have still many
failures.

…e-simd

…e-simd

So that linker substitution files are used

More changes from Ankit

Til we have the interpreter support in place

…e-simd

Til we have the interpreter support in place

And add note about opened issue

…e-simd

For * and / operators as these are not the same as vector operations.
Opened dotnet#82408 to implement
correct ones in future.

…e-simd

…e-simd