controllers/krate/versions: Use semver_ord for release_tracks where applicable

[eth3lbert]

This the follow-up PR to #10819 for the release_tracks part. :D

[Turbo87]

ah, I see. I thought you wanted to move the entire release tracks calculation into the database 😅

[eth3lbert]

ah, I see. I thought you wanted to move the entire release tracks calculation into the database 😅

ha, I actually experimented with this locally, and it is indeed doable. However, I chose to implement it as a simple start.
We can revisit this part after you get back from vacation! Btw, enjoy your vacation, have a great time :D

[eth3lbert]

I actually experimented with this locally, and it is indeed doable.

This is something I tried locally:

SELECT DISTINCT ON (rt_name) num
FROM (
    SELECT num,
           semver_ord,
           -- CASE WHEN left(num, 1) = '0' THEN '.' || split_part(num, '.', 2)
           --     ELSE split_part(num, '.', 1)
           -- END AS rt_name,
           CASE WHEN left(num, 1) = '0' THEN array[0, split_part(num, '.', 2)::int]
                ELSE array[1, split_part(num, '.', 1)::int]
           END AS rt_name
    FROM versions
    WHERE crate_id = (SELECT id FROM crates WHERE name = 'rand_core')
        AND NOT yanked -- no yanked
        AND semver_ord[3] = '{}' -- no pre-release
) t
ORDER BY rt_name DESC, semver_ord DESC;