The parent issue RHELC-1434 has the label that triggered autocreation of this subtask to track the relative story point estimation for the integration test part of the issue.

The parent issue description at the time of creation of this issue was:
As a result of RHELDST-19794 and RHELDST-22443, we can start using convert2rhel repofiles located at https://cdn-public.redhat.com/. The repofiles point to convert2rhel repositories that located at https://cdn-public.redhat.com/ as well.

Advantages:

• We don't need to take care of installing the Red Hat self-signed SSL certificate 
  /etc/rhsm/ca/redhat-uep.pem used for accessing https://cdn.redhat.com/ where we've been accessing the convert2rhel repositories. The https://cdn-public.redhat.com/ uses an SSL cert signed by a trusted Certification Authority
• Having both the repofiles and the repositories on one domain looks more trustworthy and professional. Besides that, the ftp.redhat.com is hosted by a single AWS VM, the CDN can be considered more reliable.

Acceptance criteria:

• In the code including tests, we:
  • get rid of handling the redhat-uep.pem cert
  • use the new repofile URLs on the public CDN:

    https://cdn-public.redhat.com/content/public/addon/dist/convert2rhel/server/7/7Server/x86_64/files/repofile.repo 

    https://cdn-public.redhat.com/content/public/addon/dist/convert2rhel8/8/x86_64/files/repofile.repo

  • use the new repo URLS on the public CDN:

    https://cdn-public.redhat.com/content/public/addon/dist/convert2rhel/server/7/7Server/x86_64/os/ 

    https://cdn-public.redhat.com/content/public/addon/dist/convert2rhel8/8/x86_64/os/