Keycloak prefix setting rename

[jctanner]

This variable name better matches the related keycloak setting and should be less cognitive load on sysadmins.

https://www.keycloak.org/server/all-config

[patchback]

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

❌ Failed to cleanly apply b2ddd87 on top of patchback/backports/stable-4.9/b2ddd870fdaf8ff5ecc5549e31bc5492ab72bbc3/pr-2289

Backporting merged PR #2289 into master

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/galaxy_ng.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-4.9/b2ddd870fdaf8ff5ecc5549e31bc5492ab72bbc3/pr-2289 upstream/stable-4.9

4. Now, cherry-pick PR Keycloak prefix setting rename #2289 contents into that branch:

   $ git cherry-pick -x b2ddd870fdaf8ff5ecc5549e31bc5492ab72bbc3

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

   $ git cherry-pick -m1 -x b2ddd870fdaf8ff5ecc5549e31bc5492ab72bbc3

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Keycloak prefix setting rename #2289 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/stable-4.9/b2ddd870fdaf8ff5ecc5549e31bc5492ab72bbc3/pr-2289

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-4.10: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply b2ddd87 on top of patchback/backports/stable-4.10/b2ddd870fdaf8ff5ecc5549e31bc5492ab72bbc3/pr-2289

Backporting merged PR #2289 into master

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/galaxy_ng.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-4.10/b2ddd870fdaf8ff5ecc5549e31bc5492ab72bbc3/pr-2289 upstream/stable-4.10

4. Now, cherry-pick PR Keycloak prefix setting rename #2289 contents into that branch:

   $ git cherry-pick -x b2ddd870fdaf8ff5ecc5549e31bc5492ab72bbc3

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

   $ git cherry-pick -m1 -x b2ddd870fdaf8ff5ecc5549e31bc5492ab72bbc3

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Keycloak prefix setting rename #2289 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/stable-4.10/b2ddd870fdaf8ff5ecc5549e31bc5492ab72bbc3/pr-2289

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.