Point GitHub latest release to the highest version instead of the newest one

[xeraa]

Description

https://api.github.com/repos/elastic/elasticsearch/releases/latest seems to be pointing to the (chronologically) latest release but it probably should point to the last / highest version instead. Right now it's ok with 8.17.0, but once we release another patch level version for 7.x or 8.16.x, those will be picked up instead.

Related discussion and where it came up: acidvegas/elastop#14

[elasticsearchmachine]

Pinging @elastic/es-delivery (Team:Delivery)

[breskeby]

I think our automation that creates the releases here in GitHub needs to distinguish on creation if a release should be marked as latest. There is a flag make_latest for that. I'll reach out to release eng as they own that logic.

In the meantime one workaround might be to get the releases and sort them by tag:

curl -s https://api.github.com/repos/elastic/elasticsearch/releases | jq 'sort_by(.tag_name)  | reverse | .[0]'