[browser] Wasm SDK tests

[maraf]

Now that Wasm SDK contains most of the Blazor SDK, we should test more things in the runtime

• Test that changes to the SDK doesn't break previous Blazor versions
  • Test Blazor in .NET 7 (6 behavior is the same)
  • Test Blazor in .NET 8 (current)
• Validate that built/published files match what should be there for the tested version
  • dotnet.js, dotnet.wasm, boot.config
• Validate that the content is correct
  • boot.config
• Test all the features that the SDK provides
  • Globalization
  • TimeZoneSupport
  • Jiterpreter options
  • Startup memory cache
  • Webcil
• Validate that unintended files don't appear in the build output
  • Scope this to only runtime related code (wasm template is probably a good candidate)
• Migrate tests SDK for runtime contracts from SDK repo to runtime repo

SDK repository contains a lot of these tests. Wasm.Build.Tests also contains some of these tests.

/cc @radical

[ghost]

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

Issue Details

---

Now that Wasm SDK contains most of the Blazor SDK, we should test more things in the runtime

• Test that changes to the SDK doesn't break previous Blazor versions
  • Test Blazor in .NET 7 (6 behavior is the same)
  • Test Blazor in .NET 8 (current)
• Validate that built/published files match what should be there for the tested version
  • dotnet.js, dotnet.wasm, boot.config
• Validate that the content is correct
  • boot.config
• Test all the features that the SDK provides
  • Globalization
  • TimeZoneSupport
  • Jiterpreter options
  • Startup memory cache
  • Webcil
• Validate that unintended files don't appear in the build output
  • Scope this to only runtime related code (wasm template is probably a good candidate)

SDK repository contains a lot of these tests. Wasm.Build.Tests also contains some of these tests.

/cc @radical

Author:	maraf
Assignees:	-
Labels:	arch-wasm, area-Build-mono
Milestone:	8.0.0