RFE: Allow ordering of Content View versions when updating specific version for a Composite Content View 

Overview:
---
When selecting CV versions for a CCV within the Satellite UI, the user is met with the CV versions being listed out of order with no specific pattern for how they were populated. In previous version of Red Hat Satellite, the CV versions would populate in descending order. By having them populate in a random fashion, this can make it difficult to locate the most recently published version and be error prone.

Satellite Version: satellite-6.13.4.1
---

  1. Proposed title of this feature request

     > Allow ordering of Content View versions when updating specific version for a Composite Content View 


  3. What is the nature and description of the request?

     > Fix the "new ui" to provide sorted (descending) versions of the available content view versions in a composite content view.

  4. Why does the customer need this? (List the business requirements here)

     > The current unsorted behavior makes finding and selecting the most recent view difficult and error prone.

  5. How would the customer like to achieve this? (List the functional requirements here)

     > Sort versions in descending order so that the most recently published version is at the top of the drop-down list.

  6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.

     > Create a number of content view version across several different content views.  
     > Then each CV should have a different number of views and they should not be created sequentially but rather randomly across the different CVs. 
     > Then review the version drop down for adding to a CCV.

  7. Is there already an existing RFE upstream or in Red Hat Bugzilla?

     > Unable to locate one for this specific request

  8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL8, RHEL9)?

     > ASAP, this was correct in the "old UI" and is causing workflow issues for users on the "new UI".  I'd like to see this at minimum for Sat 6.14.z, as I'm on Sat 6.13 until April 6.13.z.