Sort Simple API detail page releases

[jobselko]

📜 Checklist

• Commits are cleanly separated with meaningful messages (simple features and bug fixes should be squashed to one commit)
• A changelog entry or entries has been added for any significant changes
• Follows the Pulp policy on AI Usage
• (For new features) - User documentation and test coverage has been added

See: Pull Request Walkthrough

[jobselko]

Behaviour before this patch: https://packages.redhat.com/trusted-libraries/python/aiobotocore/

[gerrod3]

Was this requested by someone? Not sure it is needed, from the PEP:

Note that because servers may hold “legacy” data from before the adoption of PEP 440, version strings currently cannot be required to be valid PEP 440 versions, and therefore cannot be assumed to be orderable using the PEP 440 rules. However, servers SHOULD use normalised PEP 440 versions where possible.

https://peps.python.org/pep-0700/#versions

[jobselko]

@gerrod3 This was not requested, but when I started working on the yank feature, I noticed there were tens of unsorted files in Simple API and was not able to find the latest release because of this. I also remember that this used to be sorted some time ago (we did a naive sorting, for example: twine-1.1.0.tar.gz, twine-1.10.0.tar.gz, twine-1.2.0.tar.gz instead of twine-1.1.0.tar.gz, twine-1.2.0.tar.gz, twine-1.10.0.tar.gz). I will take a look at PEP-700 tomorrow.

Edit: https://pypi.org/simple/twine/ is sorted, so I would like our Simple API to be sorted as well.

[jobselko]

Updated to use the same approach as PyPI uses - https://github.com/pypi/warehouse/blob/main/warehouse/packaging/utils.py#L69