`winget upgrade --all` shouldn't install the same package more than once

[denelon]

Description of the new feature/enhancement

Some packages support "side by side" installation. Executing winget upgrade --all shouldn't attempt to install the same "latest" version of a package more than one time.

Examples:
Cura - The .exe installs separate versions into Add / Remove Programs intentionally
Unity - microsoft/winget-pkgs#16038

Proposed technical implementation details (optional)

When the command is executed, check the list of packages to be upgraded. If the same "PackageIdentifier" is found as a possible upgrade more than one time, only execute the upgrade once.

[hash-include]

Should this be of type: Issue-bug?
Re-installing same package again and again is confusing and waste of resources.

[AdrianTM]

I had a couple of R updates and had some old versions left on my system, winget didn't detect that 4.1.0 is already installed and "upgraded" these 3 versions 3 times for each run.

Name Id Version Available Source

R for Windows RProject.R 4.0.3 4.1.0 winget
R for Windows RProject.R 4.0.4 4.1.0 winget
R for Windows RProject.R 4.0.5 4.1.0 winget

If I don't remove the old versions every time when I run it winget, it tries to "upgrade" these 3 packages 3 times on each run. To me this is a bug, actually two bugs here:

1. doesn't detect the highest version (it should bail out if the highest version = current)
2. tries to upgrade each of the old version, so multiple installation of the same version

I did remove old versions, but some people might have legitimate reasons to keep multiple versions, winget should not try to upgrade anything if there are multiple versions and the highest version = current version.

[denelon]

I'll switch the labels from "Issue-Feature" to "Issue-Bug".

I'll share some of my original thinking about why I created this as a feature. When we designed the upgrade experience we didn't encounter this scenario. The client isn't throwing any exceptions. I perceived it as more of an improvement to the current experience than a bug. The current experience is clearly annoying and a waste of resources, but it is "by design".

One persons feature could always be another persons bug. Thank you both for contributing!