The pipelines can't handle slashes in "RelativeFilePath", leading to incorrectly given "Validation-No-Executables" tags.

[DandelionSprout]

Related to #318723, but is an important enough turn of events that I personally feel it warrants a separate issue thread.

I've been able to figure out a consistent red thread going through most of the packages that get Validation-No-Executables, where they are portable programs that do in fact have executables, but the pipelines seemingly can't process backslashes or forward slashes in RelativeFilePath, and therefore throws Validation-No-Executables even when there's clearly executables both in the manifest and post-installation.

Packages affected include, but are not necessarily limited to:

• New package：Microsoft.PhyloD version 2.0.0-alpha #325944
• New package: NUnit.NUnit version 4.4.0 #326326
• New package：DanielPalme.ReportGenerator version 5.5.1 #326332
• General maintenance：otya128.winevdm version 0.9.0 #326524
• New package: Benisgo.Symbolic11 version 1.3 #327215
• New package：Microsoft.MSIX-Toolkit version 10.0.19041.1 #328210
• New package: Indeepsoft.SystemDateChanger version 1.3.6 #329067
• New version: LuaLS.lua-language-server version 3.16.2 #324280
• New version: Ventoy.Ventoy version 1.1.10 #325383
• New version: sourcegit-scm.SourceGit version 2025.40 #325231
• New version: EclipseFoundation.Eclipse.Scout version 2025.09 #326071
• New version: BtbN.FFmpeg.LGPL.Shared.7.1 version 7.1.3-20251231 (2025-12-31-14-28) #327146
• New version: yt-dlp.FFmpeg version N-122319-gf6a95c7eb7-20251231 #327154
• New version: Lamdera.Lamdera version 1.4.0 #327929

[evilbananas]

Some of these I think are a bug in WinGet itself where only the first RelativeFilePath is added to the user's PATH environmental variable during a local install. #322180 (comment)

NUnit.NUnit for example, you can see after I install the manifest from your PR, it is only adding the PATH for the first one. It doesn't appear to have a problem with the slashes.