update/new does not work when additional architecture are added for a package

Brief description of your issue

wingetcreate update/new does not work when additional architecture are added for a package

Steps to reproduce

Update

wingetcreate update --out $env:TEMP -t <token> https://github.com/siderolabs/talos/releases/download/v1.9.0/talosctl-windows-amd64.exe https://github.com/siderolabs/talos/releases/download/v1.9.0/talosctl-windows-arm64.exe

Fails with:
Version https://github.com/siderolabs/talos/releases/download/v1.9.0/talosctl-windows-arm64.exe does not exist for https://github.com/siderolabs/talos/releases/download/v1.9.0/talosctl-windows-amd64.exe in the Windows Package Manager repository.

New

wingetcreate new --out $env:TEMP -t <token> https://github.com/siderolabs/talos/releases/download/v1.9.0/talosctl-windows-amd64.exe https://github.com/siderolabs/talos/releases/download/v1.9.0/talosctl-windows-arm64.exe

Fails with:
We have detected that this package identifier already exists. If you intend to update an existing package, please use the update command.

Expected behavior

Wingetcreate should update the manifest and add in the new architecture

Actual behavior

Wingetcreate fails to update package

Environment

Windows Package Manager Manifest Creator v1.9.2.0

Start by running the reported wingetcreate update and new commands with the two talosctl Windows URLs to reproduce the failures. Trace the update/new command paths involved in package identifiers and architecture handling. Done means the manifest is updated with the additional architecture instead of either command failing with the reported errors.