[browser] Expect fingerprint in dotnet.native.wasm asset identity

[maraf]

In dotnet/sdk#50949 we changed the identity of StaticWebAsset to contain fingerprint (dotnet.native.wasm -> dotnet.native.FP.wasm). This PR accommodates this when checking for dotnet.native.wasm asset from build.

The SDK change didn't flown to the runtime yet, and so Wasm.Build.Tests won't test it yet.

Contributes to dotnet/sdk#51045

[dotnet-policy-service]

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

[lewing]

/backport to release/10.0-rc2

[github-actions]

Started backporting to release/10.0-rc2: https://github.com/dotnet/runtime/actions/runs/18138997412

[pavelsavara]

Just checking: The PR that caused the regression is talking about blazor.webassembly.js. Do we have the same problem of ignoring blazor.webassembly.<FP>.js ?

[maraf]

Just checking: The PR that caused the regression is talking about blazor.webassembly.js. Do we have the same problem of ignoring blazor.webassembly.<FP>.js ?

No, blazor.js isn't affected by AOT compilation

[maraf]

Verified the change fixes the scenario with latest SDK

[Copilot]

Pull Request Overview

Updates the WebAssembly asset identity checking logic to accommodate fingerprinted filenames introduced in the SDK, where dotnet.native.wasm becomes dotnet.native.FP.wasm (where FP is a fingerprint).

• Changes exact filename matching to pattern matching for dotnet.native.wasm files
• Maintains backward compatibility with existing non-fingerprinted assets