Clear AssetGroups on framework assets at P2P project boundaries

[Copilot]

• New task ApplyStaticWebAssetFrameworkPattern that applies glob patterns to update matching SourceType=Discovered assets to SourceType=Framework
• Register task and invoke it in ResolveProjectStaticWebAssets after DefineStaticWebAssets when StaticWebAssetFrameworkPattern is set
• New target MaterializeProjectReferenceFrameworkAssets to materialize P2P framework assets at build time
• New test asset FrameworkAssetsP2PConsumer for integration testing
• Integration tests covering P2P materialization, base path rebasing, endpoint generation, and incremental builds (27 tests pass)
• Unit tests for ApplyStaticWebAssetFrameworkPattern (9 tests pass)
• All 684 unit tests pass
• Fix skipped test to use Skip parameter instead of commented-out code

[Copilot]

Pull request overview

This PR addresses a Static Web Assets transitive behavior issue where framework assets (SourceType=Framework) incorrectly retain AssetGroups metadata across P2P boundaries, causing downstream group filtering to exclude those assets (runtime 404s).

Changes:

• Clear AssetGroups for framework static web assets during ComputeReferenceStaticWebAssetItems execution (both single-asset and grouped-asset paths).
• Add unit tests to verify AssetGroups clearing for framework assets and preservation for non-framework assets.
• Extend the test helper CreateCandidate to allow specifying AssetGroups.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
src/StaticWebAssetsSdk/Tasks/ComputeReferenceStaticWebAssetItems.cs	Adds ClearAssetGroupsIfFramework and calls it when producing referenced static web assets.
test/Microsoft.NET.Sdk.StaticWebAssets.Tests/StaticWebAssets/ComputeReferenceStaticWebAssetItemsTest.cs	Adds tests covering AssetGroups clearing behavior and updates the asset factory to set AssetGroups.

Comments suppressed due to low confidence (1)

src/StaticWebAssetsSdk/Tasks/ComputeReferenceStaticWebAssetItems.cs:66

• In the grouped-assets branch, the decision to allow multiple assets to coexist at the same target path is based on AllAssetsHaveDistinctGroups(all, ...) before ClearAssetGroupsIfFramework runs. Clearing AssetGroups afterward can break that invariant (e.g., a framework asset becomes ungrouped while another asset at the same path keeps a non-empty group), which can later fail manifest validation (StaticWebAsset.ValidateAssetGroup treats multiple All assets at the same path without distinct non-empty groups as a conflict). Consider clearing AssetGroups before the distinct-groups check and then re-evaluating selection/coexistence (or skipping group-clearing when there are multiple assets for a target path and returning a deterministic single selection / explicit error).

                    // If all assets have distinct, non-empty AssetGroups, they can coexist
                    if (StaticWebAsset.AllAssetsHaveDistinctGroups(all, groupSet))
                    {
                        foreach (var groupedAsset in all)
                        {
                            if (ShouldIncludeAssetAsReference(groupedAsset, out var groupReason))
                            {
                                if (UpdateSourceType && !StaticWebAsset.SourceTypes.IsFramework(groupedAsset.SourceType))
                                {
                                    groupedAsset.SourceType = StaticWebAsset.SourceTypes.Project;
                                }
                                ClearAssetGroupsIfFramework(groupedAsset);
                                if (MakeReferencedAssetOriginalItemSpecAbsolute)
                                {
                                    groupedAsset.OriginalItemSpec = Path.GetFullPath(groupedAsset.OriginalItemSpec);
                                }

[dotnet-policy-service]

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