Avoid RH RH duplicity in Client repo name

[Lennonka]

What changes are you introducing?

Removing "Red Hat" occurence

Why are you introducing these changes? (Explanation, links to references, issues, etc.)

To avoid duplicit "Red Hat" in repo name

Anything else to add? (Considerations, potential downsides, alternative solutions you have explored, etc.)

Checklists

• [x] I am okay with my commits getting squashed when you merge this PR.
• [x] I am familiar with the contributing guidelines.

Please cherry-pick my commits into:

• [x] Foreman 3.12/Katello 4.14 (Satellite 6.16)
• [x] Foreman 3.11/Katello 4.13
• [x] Foreman 3.10/Katello 4.12
• [x] Foreman 3.9/Katello 4.11 (Satellite 6.15; orcharhino 6.8/6.9/6.10)
• [x] Foreman 3.8/Katello 4.10
• [x] Foreman 3.7/Katello 4.9 (Satellite 6.14)
• [ ] Foreman 3.6/Katello 4.8
• [ ] Foreman 3.5/Katello 4.7 (Satellite 6.13; orcharhino 6.6/6.7)
• We do not accept PRs for Foreman older than 3.5.

[github-actions[bot]]

The PR preview for aed400c9fd364938fa15f9aba693bdffb760b13a is available at theforeman-foreman-documentation-preview-pr-3296.surge.sh

The following output files are affected by this PR:

• Upgrading_Project/index-satellite.html
• Upgrading_Project_Disconnected/index-satellite.html

show diff

show diff as HTML

[Lennonka]

Cherry-picked:

• 8b3c2222cb..94729165f5 3.12 -> 3.12
• ea9832c29b..00494309f6 3.11 -> 3.11
• b70177dd68..4cfafc0fe5 3.10 -> 3.10
• 5e801b95e1..b6faa93d1b 3.9 -> 3.9
• 3e6fdef3a9..05257b8211 3.8 -> 3.8
• 9bda7fedd3..e855f380fb 3.7 -> 3.7