[Pipeline Bug]: When checking for if executables run, the pipelines scan irrelevant and unspecified executables.

#374450 has run into a case of this so big that it confuses me beyond measure.

The situation is:
* NestedInstallerType is set to `appx`
* The only filepath specified in RelativeFilePath is `tools\Appx\Microsoft.NET.CoreRuntime.2.2.appx`
* ArchiveBinariesDependOnPath is not set.
* The pipelines then proceed to **only** scan the 3 .exe-s, which are completely irrelevant to the .appx.
* It also completely ignores the one .appx file that was specified in RelativeFilePath.

The log file truly speaks for itself on how broken it's possible for a pipeline system to get:

[x86-Scope_Undefined-Locale_Undefined-Log_InstallationClient_202605150408.txt](https://github.com/user-attachments/files/27787789/x86-Scope_Undefined-Locale_Undefined-Log_InstallationClient_202605150408.txt)

Start with issue #374450 and the attached x86-Scope_Undefined-Locale_Undefined-Log_InstallationClient_202605150408.txt. Trace how the pipeline uses NestedInstallerType, RelativeFilePath, and ArchiveBinariesDependOnPath when selecting executables. Done means the pipeline checks the specified .appx rather than unrelated .exe files.

Written by the indexing model from the issue text.