feature: Allow downloading from an archive instead of git

[4e554c4c]

Did you check the docs?

• I have read all the lazy.nvim docs

Is your feature request related to a problem? Please describe.

As a neovim remote plugin developer, I would like to provide a plugin that is written in a language that is not vimscript or lua. This language must be compiled to an executable before it can be used by nvim.
I would like to distribute an archive with artifacts already built that is not my source directory.

Describe the solution you'd like

I would prefer a method to download an archive (e.g. zip or tar) from a URL (e.g. github releases) and then install a plugin from that archive as an alternative to installing directly through git.
E.g. this could be specified as

{ archive = "https://github.com/my/repo/releases/latest/download/release.zip"}

Describe alternatives you've considered

Artifacts could be placed in a separate branch, and still downloaded using git. However, this defeats the purpose of using git, since it would be difficult to preserve history and download large binary blobs.
Users could compile every release, but this is a waste of user resources and requires every user to have a build system for every remote plugin.

Additional context

Packer discussion (empty): wbthomason/packer.nvim#1210
Original issue: 4e554c4c/darkman.nvim#1

[folke]

This is a very specific use-case which is not general enough to add to lazy.
You can always provide a build step for your users that then downloads the artifacts as part of your code

[4e554c4c]

I don't think this is incredibly specific
remote plugins are built into neovim and are written in various languages (as they can't always be lua or vimscript).

I believe it would be far more scalable to implement the ability to download archives in a plugin manager than reinvent it in every remote plugin

[folke]

It is very specific, since you are the first person asking for this.