Move DR overview and reuse it in Admin

[aneta-petrova]

What changes are you introducing?

• Moving disaster recovery overview from a separate assembly in the Planning guide to the deployment path assembly
• Including the disaster recovery assembly in the Admin guide
• Renaming the disaster recovery assembly

Except for the renaming, the content stays the same.

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

As I started documenting the first of the DR scenarios (#3615), this structure seemed to work better.

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

I'm not entirely sure about the placement in the Admin guide and want to use this PR to discuss it.

Checklists

• 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:

• Foreman 3.13/Katello 4.15 (EL9 only)
• Foreman 3.12/Katello 4.14 (Satellite 6.16)
• Foreman 3.11/Katello 4.13 (orcharhino 6.11 on EL8 only; orcharhino 7.0 on EL8+EL9)
• 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)
• We do not accept PRs for Foreman older than 3.7.

[github-actions]

The PR preview for 65073a0 is available at theforeman-foreman-documentation-preview-pr-3614.surge.sh

The following output files are affected by this PR:

• Administering_Project/index-foreman-deb.html
• Administering_Project/index-foreman-el.html
• Administering_Project/index-katello.html
• Administering_Project/index-orcharhino.html
• Administering_Project/index-satellite.html
• Planning_for_Project/index-katello.html
• Planning_for_Project/index-orcharhino.html
• Planning_for_Project/index-satellite.html

show diff

show diff as HTML

[aneta-petrova]

@apinnick What do you think is the best place for disaster planning + testing + recovery? This PR places the assembly in the Admin guide -- at the very end because considering how long that guide is, I think it's kind of pointless to play with the order of the chapters.

I considered a separate guide and.. I don't know.. maybe?

(To explain a bit more: For now, this is still just an assembly with an overview. I will be adding detailed procedures for each of the DR scenarios. You can see a preview of the first scenario here if it helps #3615. Also, just in case it isn't clear from the PR: My plan is to add the scenarios to Admin only, not to Planning.)

[aneta-petrova]

Let's skip tech review because this just moves things around.