Fix long failing reporting API tests

[LadislavVasina1]

Problem Statement

Some API reporting tests did not work in the stream due to multi-CV changes.
The main goal is to get rid of Environment ID and content view ID must be provided together errors which appear due to outdated test composition.

Solution

Let the setup_org_for_a_custom_repo function create and promote CV and create AK

PRT test Cases example

trigger: test-robottelo
pytest: tests/foreman/api/test_reporttemplates.py -k "test_positive_applied_errata or test_positive_applied_errata_report_with_invalid_errata or test_positive_applied_errata_by_search"

[LadislavVasina1]

All tests failed with You must use --force to set a value other than 'enabled' as expected

[vsedmik]

Codewisely looks good to me.
We may need to wait until a fix PR for the --force issue is up and kill two flies with one stone (merge two PRs with one PRT).

[jeremylenz]

a fix PR for the --force issue is up

Katello/hammer-cli-katello#979

sorry about that ;)

[vsedmik]

trigger: test-robottelo
pytest: tests/foreman/api/test_reporttemplates.py -k "test_positive_applied_errata or test_positive_applied_errata_report_with_invalid_errata or test_positive_applied_errata_by_search"
Katello:
  hammer-cli-katello: 979

[LadislavVasina1]

trigger: test-robottelo
pytest: tests/foreman/api/test_reporttemplates.py -k "test_positive_applied_errata or test_positive_applied_errata_report_with_invalid_errata or test_positive_applied_errata_by_search"

[LadislavVasina1]

trigger: test-robottelo
pytest: tests/foreman/api/test_reporttemplates.py -k "test_positive_applied_errata or test_positive_applied_errata_report_with_invalid_errata or test_positive_applied_errata_by_search"