Move Deployment Scenarios sections into separate modules

[asteflova]

What changes are you introducing?

I'm moving all content from topics/Deployment_Scenarios.adoc to smaller modules, without making changes to the actual content.

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

To make it easier to include a new modular deployment scenario centered around AWS deployment.

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

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
• Foreman 3.12/Katello 4.14 (Satellite 6.16)
• Foreman 3.11/Katello 4.13 (orcharhino 6.11 on EL8 only)
• 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 7405df3 is available at theforeman-foreman-documentation-preview-pr-3525.surge.sh

The following output files are affected by this PR:

• Planning_for_Project/index-katello.html
• Planning_for_Project/index-orcharhino.html
• Planning_for_Project/index-satellite.html

show diff

show diff as HTML

[asteflova]

There are quite a few Vale errors reported but I'd prefer to ignore them because if I fix them, I'll feel the need to start fixing other things, and that's not what this PR is about. I'm only trying to split existing content in topics/ into smaller files to make it easier for @maximiliankolb to work on including the AWS deployment scenario. Are there any objections to this approach?

[maximiliankolb]

@asteflova I tried to make as few comments as possible. the diff proofs that you barely changed anything. I propose to have a look at #3525 (comment)

All other comments are optional. I am also very much OK applying some changes here and there after merging your PR myself in a follow-up PR.

[asteflova]

@asteflova I tried to make as few comments as possible.

Much appreciated!

the diff proofs that you barely changed anything. I propose to have a look at #3525 (comment)

All other comments are optional. I am also very much OK applying some changes here and there after merging your PR myself in a follow-up PR.

I think I addressed everything, except perhaps for one small wording suggestion.

[asteflova]

I'm going to set tech review done because the purpose of this PR is to move existing docs around and avoid changing the text. I have no doubt that the deployment scenario could use a thorough review because they seem to have been around for quite a while but this is not the right time for that.

[asteflova]

Merged to "master", no cherry-picks.