feat: allow using version ranges to cope with stale Maven Local cache

[Vampire]

With these changes you can for example depend on actions:cache__save___major:[v4,v5)" and get the latest v4 action with latest v4 typing by resolving to a concrete v4.x.y version but the output still contains just v4.
The same for actions:cache__save___minor:[v4.0,v4.1), to get the latest v4.0 but in the output just have v4.0.

[Vampire]

• feat: allow using version ranges to cope with stale Maven Local cache #1611 👈 (View in Graphite)
• fix: fix version comparison between versions with different part count #1838
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[krzema12]

I think this is the last review round 😄

[Vampire]

We'll see :-D

[krzema12]

Final2.txt

[krzema12]

@Vampire thanks, and sorry for the long wait - I'm trying my best to reduce the backlog of PRs 😄 I think the strategy to focus on mutually iterating on a single PR works really well, lets me focus properly.