Add a bullet point for migration using cloning

[AkshayGadhaveRH]

Migration using cloning is one of the possible methods for EL 8 to 9 upgrade. Since this is not mentioned in the bulleted list, it could be missed. Adding a new bullet point to mention this method.

JIRA: https://issues.redhat.com/browse/SAT-28269

What changes are you introducing?

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

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.
• [ ] I am familiar with the contributing guidelines.

Please cherry-pick my commits into:

• [X] Foreman 3.12/Katello 4.14 (Satellite 6.16)
• [ ] Foreman 3.11/Katello 4.13
• [ ] Foreman 3.10/Katello 4.12
• [ ] Foreman 3.9/Katello 4.11 (Satellite 6.15; orcharhino 6.8/6.9/6.10)
• [ ] Foreman 3.8/Katello 4.10
• [ ] 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 02a32768ec1803f38935385c12fbf949f37fb1ec is available at theforeman-foreman-documentation-preview-pr-3356.surge.sh

The following output files are affected by this PR:

• Upgrading_Project/index-foreman-el.html
• Upgrading_Project/index-katello.html
• Upgrading_Project/index-orcharhino.html
• Upgrading_Project/index-satellite.html
• Upgrading_Project_Disconnected/index-satellite.html

show diff

show diff as HTML

[asteflova]

Merged to "master" and cherry-picked:

4207685fe5..b9ddb14a2c 3.12 -> 3.12