feat(pipx): add support for specifying package extras

[antoniomdk]

Closes #2491

Some Python tools support optional features upon package installation, via pipx install package[feature,…]. This is used, for example, by Harlequin.

This PR adds support for specifying extras via

mytool = { version = '3.10', extras = 'foo,bar' }

NOTE: It only works for tools published to a registry (e.g PyPI), git-based tools require a different syntax than the one already implemented. (git+...#egg=project[...]).

NOTE: I had some issues setting up the local docker environment (unrelated to this project), so I couldn't run the e2e tests. There may be other parts of the code that could complain if using [, ] in the tool name, but the PyPI resolution error is the first one that popped up when trying to use package extras.

[jdx]

I think Tool Options would be a better solution as it wouldn't require a new convention in mise https://mise.jdx.dev/dev-tools/#tool-options

See #2515 for an example

[antoniomdk]

@jdx How would you propose the syntax for tool options in this case? Python extras are a list rather than a map, maybe something like

mytool = { version = '3.10', extras = ['bar'] }

[jdx]

I think for now unfortunately it only supports strings so you will need to do this:

mytool = { version = '3.10', extras = 'foo,bar' }

I may be wrong though, I may have implemented some simple array support

[antoniomdk]

That's fine, I'll update the PR to accommodate the tool options convention!

[antoniomdk]

@jdx I've updated the code to use ToolVersions. Not sure if we have a way to add validation for the extra field, but probably the pipx/uvx error will be informative enough.

[jdx]

you've got a test failure

[antoniomdk]

@jdx this is ready for review. The git history is kind of messy, let me know if you want me to clean it up before merging 👍