Show which .exes in multi-.exe portable ZIPs that "Failed to parse the package from (…)" errors are about.

Description of the new feature / enhancement

Occasionally when I work on Winget-pgks packages that involve portable ZIPs with a lot of .exe-s in them (with https://github.com/microsoft/winget-pkgs/pull/326858 being the recentmost case), I logically attempt to try to see how many .exe-s I can get Wingetcreate to parse properly or not.

However, as indicated by the screenshot below, there's a fair bit of trial and error involved to try to eliminate which ones that can't be parsed:

As such, additional clarifications in the error messages about which .exe-s that can't be passed, would've been splendid.

Proposed technical implementation details

For cases where Select the installer(s) from the zip archive:: are in use, change the Failed to parse the package from errors to either:

• (example.exe:) Failed to parse the package from (…)
• Failed to parse the package from(…)] (example.exe)`

Search the codebase for the error text "Failed to parse the package from" and trace the path used when selecting installers from a ZIP archive. Update that path so each parse failure identifies the relevant .exe, then verify the resulting messages for multi-.exe portable ZIPs.