[wasm/wasi] WBT: Avoid workload integrity checks on helix

[radical]

The first test in WBT run on windows can some times timeout because dotnet runs a workload integrity check before the build, adding to the time taken by the project.

At install time on the build machine, we run dotnet workload list which should do the first use checks, but IIUC, the sentinel is checked in user profile directory, and thus is dependent on the helix machine. Instead, avoid that on helix.

• [wasm/wasi] sendtohelix-*.targets: move common BuildWasmApps bits to sendtohelix-wasm.targets
• [wasm/wasi] helix.targets: add DOTNET_SKIP_WORKLOAD_INTEGRITY_CHECK=1 and DOTNET_SKIP_FIRST_TIME_EXPERIENCE=1 for wbt

Fixes #94821 .

[ghost]

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

Issue Details

---

• [wasm/wasi] sendtohelix-*.targets: move common BuildWasmApps bits to sendtohelix-wasm.targets
• [wasm/wasi] helix.targets: add DOTNET_SKIP_WORKLOAD_INTEGRITY_CHECK=1 and DOTNET_SKIP_FIRST_TIME_EXPERIENCE=1 for wbt

TODO:

• maybe run this at install time?

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

[ilonatommy]

"instead run this on build machine itself" in this PR we don't force this step. Is the check already switched on, on the build machines, so that no changes are required?

[radical]

"instead run this on build machine itself" in this PR we don't force this step. Is the check already switched on, on the build machines, so that no changes are required?

I have updated the test. We are not doing that in this PR. I need to check how we could trigger the workload integrity check for sure, as it depends on the sentinel file too which is in user config directory.