Fix displaying multiple Catalogs with the same name in the dropdown while creating a Catalog Item

[hstastna]

Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1451300

---

Steps to reproduce:

1. Enable Ansible Embedded role (not sure if this is required)
2. Add multiple (child) Tenants (Configuration > Access Control > Tenants), each Tenant has one super admin user which then creates Catalog with name 'catalog' (under Services > Catalogs > Catalogs)
3. Add Ansible Credentials and Repo (not sure if this is required)
4. Try to add new catalog item of Ansible Playbook type ( Services > Catalogs > Catalog Items )
   (or also any other type, but the BZ is mainly about Ansible Playbook type)

Before: (multiple Catalogs with the same name in the dropdown)
Adding a new Service Catalog Item:

Editing an existing Catalog Item - similar problem as the picture above

After:
Adding a new Service Catalog Item:

Editing an existing Catalog Item:

This PR:

• adds a new method available_catalogs for getting all the available catalogs with the names containing tenant names and their ancestors (if they exist) to prevent displaying multiple catalogs with the same name in the dropdown menu while creating/editing a Catalog Item or also Catalog Bundle because the same problems occurs also there
• passes the variable with the new available catalogs to angular form, for editing catalogs' names to display also tenants and their ancestors names in the drop down menu
• finally edits the original name of each catalog to get tenants and their ancestors names in the name of the Catalog

[hstastna]

@miq-bot add_label bug, gaprindashvili/yes, fine/yes

[hstastna]

@h-kataria I've found some solution for the BZ, not sure if it looks good (but it works well). Anyway, I have a question: do we want to fix the problem according to the one specific situation - while only Ansible Playbook as a Catalog Item Type is chosen? I did it so because of description in the BZ but.. don't we want the same change also for another types? Because I was able to create such catalogs so then.. see the screenshot (editing some Catalog Item of some other type):

[h-kataria]

@hstastna it should be changed for both Ansible and non-Ansible type Catalog Items to keep it consistent.

[hstastna]

@h-kataria I've made small changes in this PR, to fix the problem for both Ansible and non-Ansible type Catalog Items. It works for editing and also adding new Catalog Items, also for Catalog Bundles :)

[mzazrivec]

@h-kataria Are you OK with the above changes?

@hstastna Could you please address the codeclimate issues? Thanks.

[hstastna]

Thanks, @mzazrivec I will update the PR asap resolving codeclimate issues.

[miq-bot]

Checked commits hstastna/manageiq-ui-classic@bde7cb5~...28d90af with ruby 2.3.3, rubocop 0.52.1, haml-lint 0.20.0, and yamllint 1.10.0
2 files checked, 0 offenses detected
Everything looks fine. 🍪