wingetbot incorrectly applies `New-Package` label

Take a look at the following PRs that have both `New-Package` (a new PackageId being added) & `New-Manifest` (a version update to existing PackageId), which should be mutually exclusive.

https://github.com/microsoft/winget-pkgs/pulls?q=is%3Apr+label%3ANew-Manifest+label%3ANew-Package+is%3Aclosed

In most cases, it appears that the bot is incorrectly applying the `New-Package` label, and subsequent validation runs apply the correct `New-Manifest` label.

Start with the linked closed-PR search for items carrying both New-Package and New-Manifest, then compare their initial labels with labels after subsequent validation runs. Trace the wingetbot label decision and confirm that a new PackageId receives New-Package while a version update receives New-Manifest, but no file or entry point is named in this issue.

Written by the indexing model from the issue text.