URL-encode scoped CSS Link headers for non-ASCII project names

[Copilot]

URL-encode scoped CSS Link headers for non-ASCII project names

Description

Blazor apps with non-ASCII project names (e.g. 中文) failed at runtime due to raw non-ASCII characters in generated Link headers for scoped CSS bundles.

Fixes #51038

Customer Impact

This is required to be compliant with GB18030 and deal with cases where project names use non-ascii characters.

Regression?

• Yes
• No

9.0

Risk

• High
• Medium
• Low

Updates the manifest generation logic to ensure we URL encode path segments on the Link header. No other header that we emit needs this treatment.

Verification

• Manual (required)
• Automated

Packaging changes reviewed?

• Yes
• No
• N/A

[javiercn]

@copilot address the feedback and make sure you don't modify unrelated files.

[javiercn]

Unrelated change. Undo

[Copilot]

@copilot address the feedback and make sure you don't modify unrelated files.

Addressed feedback in commit 9e13d45:

• Reverted unnecessary RelativePath URL encoding changes (lines 235-241)
• Reverted all unrelated test file formatting changes
• Updated test to use proper RazorAppWithPackageAndP2PReference structure with library dependency named "项目"
• Only the Link header value is now URL-encoded as requested

[javiercn]

There seems to be this unrelated test failure that seems to be failing pretty consistently Microsoft.NET.Publish.Tests.GivenThatWeWantToPublishAnAotApp.Microsoft.NET.Publish.Tests.GivenThatWeWantToPublishAnAotApp.NativeAot_hw_fails_with_unsupported_host_rid(targetFramework: "net10.0")

[ilonatommy]

Tested with dogfood sdk script and blazor app.

[ilonatommy]

All failures are marked as known build errors but build analysis does not want to get green.

[ilonatommy]

/ba-g build analysis should be green, all failures are known