feat(run): match tasks to run with glob patterns

[Ajpantuso]

Summary

Closes #1271

This change make it possible to select multiple tasks to run using glob style matching.
Task topics, separated by :, are treated like directories in shell matching such that patterns like a:**:d will match tasks named a:d, a:b:d or a:b:c:d.

Additional Notes

• This brings globset in as a direct dependency, but it was transitive already.
• Used an Extension Trait since tasks_with_aliases is used in multiple places making a more local change preferable though it may make sense to move this trait or change the return type of tasks_with_aliases in the future.

[jdx]

can we go with BTreeMap? I think the output will look a little cleaner being not randomized by HashMap

IndexMap might also be a good idea but I'm not sure what order the tasks are in

[Ajpantuso]

I guess that decision would really have to be made here, but I can definitely add sorting to guarantee ordering.

[jdx]

up to you, could be in a different PR if you want. I'm not sure how many places that would need to change off the top of my head

[Ajpantuso]

Lol, played around with this a bit only to realize parallelization ends up randomizing the output ordering anyway. So I think we can defer the decision for now since ordering is only relevant for single threaded runs (which I imagine is the less likely use case).

[jdx]

clever solution using the glob here. I was just going to have a naive wildcard match

[jdx]

this could happen later, but this code should probably be updated to use glob logic as well:

mise/src/task.rs

Line 137 in 59c7216

.map(|name| match name.strip_suffix('*') {

[Ajpantuso]

this could happen later, but this code should probably be updated to use glob logic as well:

mise/src/task.rs

Line 137 in 59c7216

.map(|name| match name.strip_suffix('*') {

I can pick that up in a follow up.