Clojure CLI downloads are moving to Github releases

[puredanger]

I am preparing to move primary Clojure CLI downloads to Github releases. While I will continue publishing to download.clojure.org as a backup, Github should become the primary. This will require some changes in setup-clojure in cli.ts:

• "get latest" from https://download.clojure.org/install/stable.properties should instead use github apis to find latest release tag on https://github.com/clojure/brew-install (probably via something like https://api.github.com/repos/clojure/brew-install/releases/latest) (note that prerelease versions should not be included)
• Windows downloads should now come from "https://github.com/clojure/brew-install/releases/download/${version}/win-install.ps1"
• Linux/mac download should now come from "https://github.com/clojure/brew-install/releases/download/${version}/linux-install.sh"

The latter two will now vary depending on when we've started publishing releases, so you can either do that with 1.11.1.1379 as the boundary or (better?) trying the github urls, then failing over to the download url. The brew recipe is being set up this way as well. Please let me know if you have any questions or find anything interesting while making this change.

[DeLaGuardo]

Hi @puredanger ! New release 12.0 is available right now, but there is one problem I encountered after I merged the PR – some releases do not follow the convention you described in the issue. Here is a failed run for example - https://github.com/DeLaGuardo/setup-clojure/actions/runs/6099035886/job/16550246440
Release 1.11.1.1149 is available on Github but there is no linux-install.sh file in provided assets

[puredanger]

This is only for releases since 1.11.1.1379. I have backfilled some older releases to help some other projects migrate but no guarantees on anything older than 1.11.1.1379.

[puredanger]

The last 4 is an always increasing number, so checking just that last segment is sufficient to compare versions.

[DeLaGuardo]

I think it would be better to check the release description if expected assets are in there. I'm using that API anyway.