[mini.deps] Support `vim.version.range` in `checkout` field

[AlexKurisu]

Contributing guidelines

• I have read CONTRIBUTING.md
• I have read CODE_OF_CONDUCT.md

Module(s)

mini.deps

Description

Thanks for ongoing upstreaming of mini.deps! Maybe it's worth to add vim.version.range support to mini.deps? Your implementation of vim.pack has it, so it seems weird not to have one in mini.deps…

[echasnovski]

Thanks for the suggestion!

The vim.version.range() approach indeed came organically specifically during vim.pack development. As initial version assumed that "latest available version" is a good default to track. I still kind of think so, but it does come with problems (not all plugins use semver tags and old Vim plugins might have severely outdated tags; so default branch might make more sense).

I am yet to decide how I'll treat 'mini.deps' when vim.pack takes shape. The latter already has several approaches that I wish I'd have in 'mini.deps' (like version ranges; built-in LSP for confirmation buffer plus a more compact text).

The current standing is that I'll focus on getting vim.pack to the shape I want it to have and decide from there:

• If the final result is enough for me to recommend it over 'mini.deps', I'll just "retire" it. It will be around until 'mini.nvim' has support for Neovim=0.11 (so for a while), but on Neovim>=0.12 I'd recommend to use vim.pack. In the end, 'mini.deps' was from the start designed with a dream to be upstreamed into core.
• If not and it won't ever be (like core devs are not fond of some approaches, already present or future), then I might update 'mini.deps' with cherry-picking the best parts of vim.pack.

Currently I think the first scenario is pretty likely. So I don't think spending time on it now delivers the best value, as I'd better focus on improving vim.pack instead (it will be inevitably slower, as requires discussions/iterations/etc.).