Deprecated feature snippet

[apinnick]

What changes are you introducing?

Adding a "Deprecated snippet" for Satellite only.

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

I want to increase the visibility of deprecated features in the documentation.

This snippet is used in other Red Hat documentation repos and aligns with our downstream conventions.

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

No tech review or testing required.

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 7d47d4c is available at theforeman-foreman-documentation-preview-pr-3620.surge.sh

The following output files are affected by this PR:

show diff

show diff as HTML

[Lennonka]

I was trying to introduce a similar deprecation snippet in #3616 - please check it out.
I think that the snippet should be usable in upstream as well - can we ensure that?
Also, it could provide an alternative where available. Please, see my snippet in #3616 for illustration.

[Lennonka]

Can we cherry pick this all the way down, please? I'm going to need it for the bootstrap script deprecation.

[Lennonka]

@maximiliankolb This is the official RH wording -- if you prefer a different wording for orcharhino, now is the time to speak out.

[Lennonka]

We've decided to add the snippet in the scope of #3616. Closing this PR.