Add default StaticWebAssetMakeReferencedAssetOriginalItemSpecAbsolute for WebAssembly apps

[Copilot]

This PR adds the missing StaticWebAssetMakeReferencedAssetOriginalItemSpecAbsolute property to the WebAssembly props file to ensure it has a default value when not explicitly set.

The change adds a single line to Microsoft.NET.Sdk.WebAssembly.Browser.props:

<StaticWebAssetMakeReferencedAssetOriginalItemSpecAbsolute Condition="'$(StaticWebAssetMakeReferencedAssetOriginalItemSpecAbsolute)' == ''">true</StaticWebAssetMakeReferencedAssetOriginalItemSpecAbsolute>

This mirrors the same pattern already implemented in the Blazor SDK at Microsoft.NET.Sdk.BlazorWebAssembly.Current.props and ensures that WebAssembly applications have consistent behavior with static web asset handling.

Without this property being set, WebAssembly applications may experience issues with static web asset path resolution, as described in the related ASP.NET Core issue.

Fixes #118393.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[Copilot]

Pull Request Overview

This PR adds a missing default property value for WebAssembly applications to ensure consistent static web asset handling behavior. The change addresses an issue where WebAssembly apps may experience problems with static web asset path resolution due to the absence of this property.

• Adds default value for StaticWebAssetMakeReferencedAssetOriginalItemSpecAbsolute property
• Ensures consistency with Blazor SDK implementation
• Fixes static web asset path resolution issues in WebAssembly applications

[ilonatommy]

the job that is running for 14 hours finished, the information about it was just lost somewhere on the way:

@akoeplinger Do you know a way to stop waiting for the result (abort running etc) or do I have to merge with main/close-open the PR to let it be mergeable?

[akoeplinger]

@akoeplinger Do you know a way to stop waiting for the result (abort running etc) or do I have to merge with main/close-open the PR to let it be mergeable?

this was due to the GitHub outage and the only way is close/reopen or merge main since AzDO is already green so the job can't be retriggered.

that said, since we only require the Build Analysis check in runtime another option would've been forcing that to green with /ba-g