Support retirement of bundled services in ascending / descending order

[dmetzger57]

Associated BZ https://bugzilla.redhat.com/show_bug.cgi?id=1608763

If the catalog bundle is being created, the creation of the catalog, the action order and provision order are defined, this order is taken during the provisioning of the catalog bundled and it works correctly.

During the retirement, the catalog items owned to a catalog bundle are retired at the same time. In some cases, it is better to have the option to set the order of the actions in ascending or descending priority.

Examples: Creation: Catalog bundle1 Catalog item1 -> create vm -> priority 1 Catalog item2 ansible tower -> register to satellite -> priority 2 Catalog item3 ansible tower-> install software middleware-> priority 3

Retirement: Retire the catalog bundle launch priority 2 wait and launch priority 1 Catalog item2 ansible tower -> unregister to

[miq-bot]

This issue has been automatically marked as stale because it has not been updated for at least 3 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

Thank you for all your contributions! More information about the ManageIQ triage process can be found in the traige process documentation.