[browser] Update wasmbrowser template

[maraf]

• Backport Fixed devtools url used for debug with chrome and edge aspnetcore#61813 to DevServer in Wasm SDK
• Fingerprint user javascript files in wasmbrowser template

[dotnet-policy-service]

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

[Copilot]

Pull Request Overview

This PR backports a change to the Wasm SDK DevServer and adds a fingerprinting mechanism for user JavaScript files in the browser template. Key changes include:

• Adding a StaticWebAssetFingerprintPattern for "*.js" files in the browser template.
• Updating the DevServer’s WebAssemblyNetDebugProxyAppBuilderExtensions to normalize the DevTools frontend URL via a local function.

Reviewed Changes

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

File	Description
src/mono/wasm/templates/templates/browser/browser.0.csproj	Added fingerprinting configuration for JavaScript files to support asset caching.
src/mono/wasm/host/DevServer/WebAssemblyNetDebugProxyAppBuilderExtensions.cs	Refactored DevTools URL construction to handle absolute and relative URLs by normalizing them.

Comments suppressed due to low confidence (1)

src/mono/wasm/host/DevServer/WebAssemblyNetDebugProxyAppBuilderExtensions.cs:455

• Ensure that the variable 'query' extracted via UriHelper.FromAbsolute includes the proper leading '?' when concatenated. If it does not, consider adding the '?' prefix to form a valid URL.

return "${DefaultBrowserDevToolsPagePath}${query}";

[maraf]

/ba-g Failure is not related