[browser] Use WebAssembly SDK for runtime tests

[maraf]

• One of the goals of this PR is to use WasmSDK in most standard way and avoid too much deviation just for runtime repo
• Hook WasmSDK pack into InTree build
• Remove WasmAppBuilder and targets around it
• Move AOT & EAT smoke tests from Helix to AzDo. We don't support "AOT on Helix" in WasmSDK because of the way how build is composed. The whole set of tests won't finish there, but we don't run it on runtime pipeline. It would require a significant amount of work. We have options if we need it later
• Remove minimal-config sample as we have a proper way to generate bundler-friendly boot config
• MSBuild tests changes have brief explanations why they are neded
• Library tests don't follow the convention that StaticWebAssetsSDK expects. We have LinkContentToWwwroot task to manipulate incoming @(Content) and $(PublishDir) files to the shape that can be consumed by SWA and accessible at some URL (in the wwwroot)
• Remove unused WasmInvariantGlobalization
• Fix paths for WasmRunWasmOpt

Fixes #103025

TODO

• Copy to library test output
  • test-main.js
  • index.html
  • WasmTestRunner.dll as mainAssembly
  • WasmSymbolicator.dll
  • wasm-symbol-patterns.txt
• Pack.Tasks for TrimmingTests
• Exclude XHarness plugins (WasmSymbolicator.dll) from AOT compilation
  • The reason why it's failing here is that <Content Link="..." copy the assembly to the publish output early enough, so that it gets picked up to WasmAssembliesToBundle and so the AOT compiler gets it
• NetCoreServer and RemoteLoopServer GetCurrentProjectBuildStaticWebAssetItems
• Support WasmFilesToIncludeInFileSystem - We needed coreVfs for runtimeConfig, but we have that solved now by embedding it into the boot manifest. I think we can drop coreVfs. The challenge is that VFS items has targetPath as well, so SWA standard properties aren't enough
  • Update Identity to match relative requirement from [browser] Support WasmFilesToIncludeInFileSystem in WasmSdk #120970
• Support IncludeSatelliteAssembliesInVFS (it's not used anywhere anymore)
  • Implement it only in tests.targets
• browser-wasm linux Release LibraryTests_EAT (aka AOTonHelix)
  • Use Wasm.Build.Tests infrastructure
  • tests.proj
    • RunSmokeTestsOnly=true
    • RunHighAOTResourceRequiringTestsOnly=true
  • ProxyProjectForAOTOnHelix.proj is using WasmApp.LocalBuild.props/targets
  • Update default target. For AOT it does AOT compilation, but it doesn't invoke "Build". The .NET build runs on AzDO, WasmBuild runs on Helix
    • Run PrepareForRun (DependsOn) for SWA
    • Run ComputeAndCopyFilesToPublishDirectory for SWA
  • WasmAppDir
  • Support AOT in build
• <OutputType Condition="'$(OutputType)' == ''">exe</OutputType> in Microsoft.NET.Sdk.WebAssembly.Browser.props is too relaxed as at the point the default value of library is already supplied by general SDK props
• Library tests are doing native relink
• FunctionalTests
  • StartupHookForFunctionalTest.csproj
• Wasm.Advanced.Sample.csproj has WasmAssembliesToBundle item is empty
• StartupHookForFunctionalTest conflicting SWA Microsoft.CSharp.wasm
• If we unhook all WasmSDK targets from in nested publish, IncrementalClean will delete the files in bin folder
• Library tests are not loading ICU correctly
  • InvariantGlobalization is empty, results in _WasmInvariantGlobalization=true
  • Follow WasmIncludeFullIcuData
• Remove WasmAppBuilder and related targets
  • Remove WasmExtraFilesToDeploy from tests
  • <WasmEnvironmentVariable Include="DOTNET_DiagnosticPorts" Value="$(DiagnosticPorts)" Condition="'$(DiagnosticPorts)' != ''"/>
• TrimmingTests
  • InvariantGlobalization
• RuntimeTests
  • dotnet.js is just boot config, it doesn't contain the loader script

[maraf]

/azp run runtime-wasm

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[maraf]

/azp run runtime-wasm

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[maraf]

/azp run runtime-wasm

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[radekdoulik]

Nice to see that simplified, thank you. Looking forward to coreclr changes on top of that.

LGTM, does any documentation need change too? Doesn't need to be done in this PR though.

[pavelsavara]

/azp run runtime-wasm

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[pavelsavara]

/azp run runtime-wasm

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[maraf]

Extended set of Smoke_AOT tests passed

[maraf]

does any documentation need change too?

I have change what I encounter on the road. I think we need to do some more house cleaning when we introduce a native build for CoreCLR.

[maraf]

/ba-g Wasm.Build.Tests and CoreCLR failures are not related