Change Getting started EE guide reference to point to the relevant location

[Andersson007]

Change Getting started EE guide reference to point to the relevant location

[oraNod]

Thanks @Andersson007

[felixfontein]

Approving SC related part.

[Andersson007]

@oraNod @felixfontein thanks for reviewing!

[patchback]

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

❌ Failed to cleanly apply 9f3e3f4 on top of patchback/backports/stable-2.15/9f3e3f4b7c3b9335f5488bb6150c7397ba18e039/pr-1877

Backporting merged PR #1877 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/9f3e3f4b7c3b9335f5488bb6150c7397ba18e039/pr-1877 upstream/stable-2.15

4. Now, cherry-pick PR Change Getting started EE guide reference to point to the relevant location #1877 contents into that branch:

   $ git cherry-pick -x 9f3e3f4b7c3b9335f5488bb6150c7397ba18e039

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

   $ git cherry-pick -m1 -x 9f3e3f4b7c3b9335f5488bb6150c7397ba18e039

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Change Getting started EE guide reference to point to the relevant location #1877 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/stable-2.15/9f3e3f4b7c3b9335f5488bb6150c7397ba18e039/pr-1877

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.

[patchback]

Backport to stable-2.16: 💚 backport PR created

✅ Backport PR branch: patchback/backports/stable-2.16/9f3e3f4b7c3b9335f5488bb6150c7397ba18e039/pr-1877

Backported as #1879

🤖 @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/9f3e3f4b7c3b9335f5488bb6150c7397ba18e039/pr-1877

Backported as #1880

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

[Andersson007]

Ah, as @oraNod pointed out in another PR, the guides simply don't exist in stable-2.15, so no need to backport to it