[browser-wasm] Support Mono runtime components in workload

[lambdageek]

The browser-wasm workload should support selecting different mono runtime components (#50862) for different configurations.

This depends on #54417

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

Issue Details

---

The browser-wasm workload should support selecting different mono runtime components (#50862) for different configurations.

This depends on #54417

Author:	lambdageek
Assignees:	-
Labels:	area-VM-meta-mono, untriaged
Milestone:	-

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

Issue Details

---

The browser-wasm workload should support selecting different mono runtime components (#50862) for different configurations.

This depends on #54417

Author:	lambdageek
Assignees:	-
Labels:	arch-wasm, area-VM-meta-mono
Milestone:	-

[radical]

From Wasm targets pov, they will get a list of files to link for dotnet.js/wasm?

[lambdageek]

From Wasm targets pov, they will get a list of files to link for dotnet.js/wasm?

The workflow will be the same for all workloads:

1. Populate @(_MonoComponents) with the components you want for example "" or "hot_reload;diagnostics_tracing" or "hot_reload" etc
2. Call the _MonoSelectRuntimeComponents target at the appropriate time in your build
3. Combine @(_MonoRuntimeComponentLink) with the full path of the native/ directory of your runtime pack and link those libraries together with libmonosgen-2.0.a when building your host.
4. You now have an app bundle with components (or component stubs, depending on what you chose)