Description

The wrong collection can be listed as the `latest` in the collection's page version drop down. The namespace page will show the real latest version and clicking on the collection from the namespace page will default to opening to the real latest version. 

Steps to Reproduce

Go to the rhel_system roles collection main page: https://console.redhat.com/ansible/automation-hub/repo/published/redhat/rhel_system_roles/

Click on the collection version drop down, and the collection showing "(latest)" is the v1.7.3 version, not the actual latest, v1.21.1. 

The list comes from the URL: https://console.redhat.com/api/automation-hub/v3/plugin/ansible/search/collection-versions/?repository_name=published&namespace=redhat&name=rhel_system_roles&order_by=-version&offset=0&limit=10

James Tanner theorized that:

The order_by=-version param isn't working as expected on x-repo search, so the ui is getting the whole list and 1.7.3 shows up first and it's just marking it "latest", although it got the real "latest" from a previous query so it shows that one by default on the page.

Version Info: 

"server_version":"4.8.0dev"

"galaxy_ng_version":"4.8.0dev"

galaxy_ng_commit":"origin/master:a314e11"

"galaxy_importer_version":"0.4.10"

"pulp_core_version":"3.23.4"

"pulp_ansible_version":"0.17.2"

"pulp_container_version":"2.14.5"