feat(update): adding --interactive option for pixi update

[prady0t]

Description

Adds an interactive menu option when pixi update.

Fixes #4734

How Has This Been Tested?

Running' pixi update --interactive shows the interactive menu.

AI Disclosure

• This PR contains AI-generated content.
  • I have tested any AI-generated content in my PR.
  • I take responsibility for any AI-generated content in my PR.

Tools: GitHub Copilot (used for generating the interactive menu using dialouger)

Checklist:

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have added sufficient tests to cover my changes.
• I have verified that changes that would impact the JSON schema have been made in schema/model.py.

[prady0t]

@ruben-arts This PR includes a very basic prototype of the update menu. Currently, it displays all packages across all platforms and envs hence the list is long.

We can extend this to only show specific packages, for example, pixi update --interactive --platform osx-arm64 shows only osx specific packages to select from. It also currently misses out on the final and current package info in the menu.

[ruben-arts]

Hmm, this is a bit long. A few ideas to improve this:

• Make it searchable with typing
• Add the "current" and "latest" versions
• Sort on explicit first or other sort options.

I'm not sure how much it's worth the maintenance, as this could also be an extension, perhaps.

[prady0t]

I'm not sure how much it's worth the maintenance, as this could also be an extension, perhaps.

I really like that idea and would be willing to work on it. Should I move this work + the suggestions into a pixi-interactive extension? This would work for both update and upgrade.

[ruben-arts]

I really like that idea and would be willing to work on it. Should I move this work + the suggestions into a pixi-interactive extension? This would work for both update and upgrade.

I like your work, so if you do another iteration in pixi itself maybe I would be convinced to take on the ownership of the code. As I also like the idea 👍

[prady0t]

@ruben-arts With the current commit, it also prints the current version (it doesn't look pretty yet). For the latest or the max upgradable version, will we have to run an update dry-run? That would be time-consuming. Are there any more ways?

[ruben-arts]

I don't think the solve is mendatory, you could match the spec with the repodata to get the target and latest. Without actually solving.
e.g. `python = ">=3.12, <3.13"

> pixi update --interactive
package     current    target    latest
--------    -------    ------    ------
python      3.12.1     3.12.9    3.14.2