[browser] Use WebAssembly SDK for runtime tests

[maraf]

TBD

Contributes to #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
• Remove WasmExtraFilesToDeploy from tests
• 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

[dotnet-policy-service]

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

[maraf]

@javiercn Does it ring any bell?

D:\a\_work\1\s\src\libraries\Common\tests\System\Net\Prerequisites\NetCoreServer\NetCoreServer.csproj error MSB4057: The target "GetCurrentProjectBuildStaticWebAssetItems" does not exist in the project. [D:\a\_work\1\s\src\libraries\Common\tests\System\Net\Prerequisites\NetCoreServer\NetCoreServer.csproj]

browser-wasm windows Release LibraryTests Build.binlog