Pin hot reaload wasm browser package version

[ilonatommy]

Similar to #52517 but fixes dotnet/aspnetcore#65261.

Testing:

• build sdk
• run dotnet pack ".\src\BuiltInTools\HotReloadAgent.WebAssembly.Browser\Microsoft.DotNet.HotReload.WebAssembly.Browser.csproj" -c Debug -o ".\artifacts\packages\Debug\Shipping" /p:Version=11.0.100-preview.1.26078.107 to create the missing net11 package
• take it and copy it to local net11 nuget cache Expand-Archive -Path $nupkg -DestinationPath "C:\Nuget\microsoft.dotnet.hotreload.webassembly.browser\11.0.100-preview.1.26078.107" -Force
• Rerun the steps from the issue and see the problem is gone

[dotnet-policy-service]

Thanks for your PR, @@ilonatommy.
To learn about the PR process and branching schedule of this repo, please take a look at the SDK PR Guide.

[Copilot]

Pull request overview

This PR adds .NET 11.0 target framework support for the HotReload WebAssembly Browser package to fix a missing package version issue when building .NET 11 WebAssembly applications.

Changes:

• Added AgentTargetFrameworkV11 property for .NET 11.0 assemblies injected into apps
• Updated WebAssembly.Browser project to multi-target both net10.0 and net11.0
• Clarified that AgentTargetFrameworkV10 is specifically for .NET 10.0 (not 10.0+)

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
src/BuiltInTools/Watch/TargetFrameworks.props	Adds AgentTargetFrameworkV11 property and updates V10 comment to be more precise
src/BuiltInTools/HotReloadAgent.WebAssembly.Browser/Microsoft.DotNet.HotReload.WebAssembly.Browser.csproj	Imports TargetFrameworks.props and multi-targets net10.0 and net11.0 to ensure compatibility with both runtime versions

[tmat]

Do we actually need to target .NET 11? Wouldn't pinning to net10 work?

[tmat]

Let's remove the package instead: @maraf is working on it here: #52710