[wasm] Enable wasm relinking for Trimming tests running in `dotnet-linker-tests`

[radical]

We do wasm relinking in some cases by default now (eg. in Release config). This breaks in case of Trimming tests run under dotnet-linker-tests, because it cannot find mono-aot-cross. It needs this to essentially invoke:

"$(MonoAotCrossCompilerPath)" --print-icall-table > "$(_WasmIntermediateOutputPath)runtime-icall-table.h"

Wasm relinking has been disabled in this case, for now (#49774). But this needs to be fixed.

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.

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

Issue Details

---

We do wasm relinking in some cases by default now (eg. in Release config). This breaks in case of Trimming tests run under dotnet-linker-tests, because it cannot find mono-aot-cross. It needs this to essentially invoke:

"$(MonoAotCrossCompilerPath)" --print-icall-table > "$(_WasmIntermediateOutputPath)runtime-icall-table.h"

Wasm relinking has been disabled in this case, for now (#49774). But this needs to be fixed.

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

[ilonatommy]

Have we made any progress here @radekdoulik?

[lewing]

Considering this resolved