[browser] Migrate WebAssemblyHotReloadCapabilities from Blazor to WasmSDK

[maraf]

In dotnet/sdk#49800 we are introducing a HotReload package that will be automatically referenced by WasmSDK and usable for all WebAssembly in browser scenarios. We need to set HotReload capabilities in a common place.

In .NET 8+ the runtime capabilities are the same.

Manually tested that HotReload is able to pick the value after removing it from Blazor

dotnet watch ⌚ [BlazorWasmHotReloadV2Sdk (net10.0)] Project 'BlazorWasmHotReloadV2Sdk (net10.0)' specifies capabilities: 'TEST Baseline AddMethodToExistingType AddStaticFieldToExistingType NewTypeDefinition ChangeCustomAttributes AddInstanceFieldToExistingType GenericAddMethodToExistingType GenericUpdateMethod UpdateParameters GenericAddFieldToExistingType'

Contributes to dotnet/aspnetcore#61272

[maraf]

cc @tmat

[Copilot]

Pull Request Overview

This PR migrates WebAssembly Hot Reload capabilities configuration from Blazor-specific settings to the broader WasmSDK, making Hot Reload functionality available for all WebAssembly browser scenarios. This change supports the introduction of a new HotReload package in the SDK that will be automatically referenced by WasmSDK.

Key changes:

• Moves .NET version detection logic to an earlier PropertyGroup for reuse
• Adds WebAssemblyHotReloadCapabilities property with framework-specific capability sets
• Removes duplicate version detection code from the _ResolveWasmConfiguration target

[dotnet-policy-service]

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

[maraf]

/ba-g Timeouts are covered in other architecture legs

[tmat]

lgtm