release_and_maintenance: mark 8.x unmaintained as 8.7.0 released

[chenrui333]

since 8.7.0 got released, it would make sense to mark 8.x as unmaintained

• relates to [ansible] 8.7.0 is final release for 8.x endoflife-date/endoflife.date#5170

[ansible-documentation-bot]

Thanks for your Ansible docs contribution! We talk about Ansible documentation on matrix at #docs:ansible.im and on libera IRC at #ansible-docs if you ever want to join us and chat about the docs! We meet there on Tuesdays (see the Ansible calendar) and welcome additions to our weekly agenda items - scroll down to find the upcoming agenda and add a comment to put something new on that agenda.

[patchback]

Backport to stable-2.15: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply 35cd44b on top of patchback/backports/stable-2.15/35cd44b33f2d095154e0982b12b9cb112a4d31a4/pr-1522

Backporting merged PR #1522 into devel

1. Ensure you have a local repo clone of your fork. Unless you cloned it
   from the upstream, this would be your origin remote.
2. Make sure you have an upstream repo added as a remote too. In these
   instructions you'll refer to it by the name upstream. If you don't
   have it, here's how you can add it:

   $ git remote add upstream https://github.com/ansible/ansible-documentation.git

3. Ensure you have the latest copy of upstream and prepare a branch
   that will hold the backported code:

   $ git fetch upstream
   $ git checkout -b patchback/backports/stable-2.15/35cd44b33f2d095154e0982b12b9cb112a4d31a4/pr-1522 upstream/stable-2.15

4. Now, cherry-pick PR release_and_maintenance: mark 8.x unmaintained as 8.7.0 released #1522 contents into that branch:

   $ git cherry-pick -x 35cd44b33f2d095154e0982b12b9cb112a4d31a4

   If it'll yell at you with something like fatal: Commit 35cd44b33f2d095154e0982b12b9cb112a4d31a4 is a merge but no -m option was given., add -m 1 as follows instead:

   $ git cherry-pick -m1 -x 35cd44b33f2d095154e0982b12b9cb112a4d31a4

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR release_and_maintenance: mark 8.x unmaintained as 8.7.0 released #1522 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/stable-2.15/35cd44b33f2d095154e0982b12b9cb112a4d31a4/pr-1522

7. Create a PR, ensure that the CI is green. If it's not — update it so that
   the tests and any other checks pass. This is it!
   Now relax and wait for the maintainers to process your pull request
   when they have some cycles to do reviews. Don't worry — they'll tell you if
   any improvements are necessary when the time comes!

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

[samccann]

Cool thanks for this! And welcome to the Ansible project!

[patchback]

Backport to stable-2.16: 💚 backport PR created

✅ Backport PR branch: patchback/backports/stable-2.16/35cd44b33f2d095154e0982b12b9cb112a4d31a4/pr-1522

Backported as #1525

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

[patchback]

Backport to stable-2.17: 💚 backport PR created

✅ Backport PR branch: patchback/backports/stable-2.17/35cd44b33f2d095154e0982b12b9cb112a4d31a4/pr-1522

Backported as #1526

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

[chenrui333]

Thanks for merging the fix! 👍