Value Statement

When selecting Ansible job/workflow templates and the inventory to use for automation templates, the user currently must go by name alone.

Both of these Ansible resources can have a description, and we should display it when available. We can also provide a link to the Ansible Tower UI where the user can examine/edit the resources in more detail.

Definition of Done for Engineering Story Owner (Checklist)

• Dropdowns listing inventory and Ansible templates show the description for these items when available. This applies when creating or editing an Automation template.
• When a value is selected in the dropdowns, a link is provided to view the inventory or template on Ansible Tower.

Development Complete

• The code is complete.
• Functionality is working.
• Any required downstream Docker file changes are made.

Tests Automated 

• [X] Unit/function tests have been automated and incorporated into the
  build.
• [ ] 100% automated unit/function test coverage for new or changed APIs.

Secure Design

• [ ] Security has been assessed and incorporated into your threat model.

Multidisciplinary Teams Readiness

• [X] Create an informative documentation issue using the [Customer
  Portal_doc_issue template](
  https://github.com/stolostron/backlog/issues/new?assignees=&labels=squad%3Adoc&template=doc_issue.md&title=),
  and ensure doc acceptance criteria is met. Link the development issue to
  the doc issue. https://issues.redhat.com/browse/ACM-5003
• [X] Provide input to the QE team, and ensure QE acceptance criteria
  (established between story owner and QE focal) are met.

Support Readiness

• [ ] The must-gather script has been updated.