Helm chart install page: start structural revisions

What does this MR do?

Now that !5030 (merged) is merged, let's start moving the subheadings into a more logical order. This MR modifies:

• Move ## Configuring GitLab Runner using the Helm Chart above the Install subheading, as it's essentially a long and complex prerequisite
• Handle subheadings of ## Configuring GitLab Runner using the Helm Chart:
  • blend child subheading ### Required configuration (child) back into it
  • move child subheading ### Additional configuration from H3 to H2, and bump those to the bottom of the page to get a cleaner flow through the major CRUD steps
  • because Additional configuration changed a H2, update the heading levels for the subheadings underneath
• Move ## Check available GitLab Runner Helm Chart versions from an H2 further down the page, to a H3 nested underneath Installing, because the Installing subheading ends with a description of selecting a chart version.
• Move ## Uninstalling GitLab Runner using the Helm Chart above all the additional configuration options, to keep the major parts of CRUD together.

Related issues

• Follow-up to Address line-level findings in Kubernetes insta... (!5030 - merged)
• Related to technical-writing#1075

Author's checklist

• Optional. Consider taking the GitLab Technical Writing Fundamentals course.
• Follow the:
  • Documentation process.
  • Documentation guidelines.
  • Style Guide.
• If you're adding or changing the main heading of the page (H1), ensure that the product tier badge is added.
• If you are a GitLab team member, request a review based on:
  • The documentation page's metadata.
  • The associated Technical Writer.

If you are a GitLab team member and only adding documentation, do not add any of the following labels:

• ~"frontend"
• ~"backend"
• ~"type::bug"
• ~"database"

These labels cause the MR to be added to code verification QA issues.

Reviewer's checklist

Documentation-related MRs should be reviewed by a Technical Writer for a non-blocking review, based on Documentation Guidelines and the Style Guide.

If you aren't sure which tech writer to ask, use roulette or ask in the #docs Slack channel.

• If the content requires it, ensure the information is reviewed by a subject matter expert.
• Technical writer review items:
  • Ensure docs metadata is present and up-to-date.
  • Ensure the appropriate labels are added to this MR.
  • Ensure a release milestone is set.
  • If relevant to this MR, ensure content topic type principles are in use, including:
    • The headings should be something you'd do a Google search for. Instead of Default behavior, say something like Default behavior when you close an issue.
    • The headings (other than the page title) should be active. Instead of Configuring GDK, say something like Configure GDK.
    • Any task steps should be written as a numbered list.
    • If the content still needs to be edited for topic types, you can create a follow-up issue with the docs-technical-debt label.
• Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review.

docs/install/kubernetes.md

@@ -66,6 +66,32 @@ To install GitLab Runner by using the Helm chart:
      to your `helm install` command. You can install any version of the chart, but more recent `values.yml` might
      be incompatible with older versions of the chart.
 
+### Check available GitLab Runner Helm Chart versions
+
+Helm Chart and GitLab Runner do not follow the same versioning. To see version mappings
+between the two, run the command for your version of Helm:
+
+```shell
+# For Helm 2
+helm search -l gitlab/gitlab-runner
+
+# For Helm 3
+helm search repo -l gitlab/gitlab-runner
+```
+
+An example of the output:
+
+```plaintext
+NAME                  CHART VERSION APP VERSION DESCRIPTION
+gitlab/gitlab-runner  0.64.0        16.11.0     GitLab Runner
+gitlab/gitlab-runner  0.63.0        16.10.0     GitLab Runner
+gitlab/gitlab-runner  0.62.1        16.9.1      GitLab Runner
+gitlab/gitlab-runner  0.62.0        16.9.0      GitLab Runner
+gitlab/gitlab-runner  0.61.3        16.8.1      GitLab Runner
+gitlab/gitlab-runner  0.61.2        16.8.0      GitLab Runner
+...
+```
+
 ## Upgrading GitLab Runner using the Helm Chart
 
 Prerequisites:
@@ -75,7 +101,7 @@ Prerequisites:
   [authorization errors when they complete](../faq/index.md#helm-chart-error--unauthorized).
 - You've ensured all jobs have completed.
 
-Use `helm upgrade` to change configuration or update charts, changing parameters as needed:
+To change your configuration or update charts, use `helm upgrade`, changing parameters as needed:
 
 ```shell
 helm upgrade --namespace <NAMESPACE> -f <CONFIG_VALUES_FILE> <RELEASE-NAME> gitlab/gitlab-runner
@@ -89,41 +115,30 @@ helm upgrade --namespace <NAMESPACE> -f <CONFIG_VALUES_FILE> <RELEASE-NAME> gitl
 - To update to a specific version of the GitLab Runner Helm Chart, rather than the latest one, add
   `--version <RUNNER_HELM_CHART_VERSION>` to your `helm upgrade` command.
 
-## Check available GitLab Runner Helm Chart versions
+## Uninstalling GitLab Runner using the Helm Chart
 
-Versions of Helm Chart and GitLab Runner do not follow the same versioning.
-Use the command below to get version mappings between Helm Chart and GitLab Runner:
+To uninstall GitLab Runner:
 
-```shell
-# For Helm 2
-helm search -l gitlab/gitlab-runner
+1. Pause the runner in GitLab, and ensure any jobs have completed. This prevents job-related problems, such as
+   [authorization errors on completion](../faq/index.md#helm-chart-error--unauthorized).
+1. Run, this command, modifying it as needed:
 
-# For Helm 3
-helm search repo -l gitlab/gitlab-runner
-```
-
-An example of the output:
+   ```shell
+   helm delete --namespace <NAMESPACE> <RELEASE-NAME>
+   ```
 
-```plaintext
-NAME                  CHART VERSION APP VERSION DESCRIPTION
-gitlab/gitlab-runner  0.64.0        16.11.0     GitLab Runner
-gitlab/gitlab-runner  0.63.0        16.10.0     GitLab Runner
-gitlab/gitlab-runner  0.62.1        16.9.1      GitLab Runner
-gitlab/gitlab-runner  0.62.0        16.9.0      GitLab Runner
-gitlab/gitlab-runner  0.61.3        16.8.1      GitLab Runner
-gitlab/gitlab-runner  0.61.2        16.8.0      GitLab Runner
-...
-```
+   - `<NAMESPACE>` is the Kubernetes namespace where GitLab Runner is installed.
+   - `<RELEASE-NAME>` is the name you gave the chart when you installed it.
+     In the [installation section](#installing-gitlab-runner-using-the-helm-chart) of this page, we called it `gitlab-runner`.
 
 ## Configuring GitLab Runner using the Helm Chart
 
-Create a `values.yaml` file for your GitLab Runner configuration. See
-[Values Files](https://helm.sh/docs/chart_template_guide/values_files/) in the Helm documentation
-for information on how your values file overrides the defaults.
+Store your GitLab Runner configuration changes in `values.yaml`. For help configuring this file, see:
 
-The default configuration is always available in the
-[`values.yaml`](https://gitlab.com/gitlab-org/charts/gitlab-runner/blob/main/values.yaml)
-in the chart repository.
+- The default [`values.yaml`](https://gitlab.com/gitlab-org/charts/gitlab-runner/blob/main/values.yaml)
+  configuration in the chart repository.
+- The Helm documentation for [Values Files](https://helm.sh/docs/chart_template_guide/values_files/), which explains
+  how your values file overrides the default values.
 
 ### Required configuration
 
@@ -135,12 +150,6 @@ For GitLab Runner to function, your configuration file **must** specify the foll
   - The authentication token you obtain when you [create a runner in the GitLab UI](https://docs.gitlab.com/ee/ci/runners/runners_scope.html#create-an-instance-runner-with-a-runner-authentication-token).
   - Set the token directly or [store it in a secret](#store-registration-tokens-or-runner-tokens-in-secrets).
 
-  \- or -
-
-- `runnerRegistrationToken` ([deprecated](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/102681) in GitLab 15.6):
-  - The registration token [retrieved from your GitLab instance](https://docs.gitlab.com/ee/ci/runners/).
-  - Set the token directly or [store it in a secret](#store-registration-tokens-or-runner-tokens-in-secrets).
-
 Unless you need to add more configuration, you are
 ready to [install GitLab Runner](#installing-gitlab-runner-using-the-helm-chart).
 
@@ -627,21 +636,3 @@ runners:
           [runners.kubernetes]
             helper_image_flavor = "ubi-fips"
 ```
-
-## Uninstalling GitLab Runner using the Helm Chart
-
-Before uninstalling GitLab Runner, pause the runner in GitLab and ensure any jobs have completed.
-Pausing the runner prevents problems arising with the jobs, such as
-[authorization errors when they complete](../faq/index.md#helm-chart-error--unauthorized).
-
-To uninstall the GitLab Runner Chart, run the following:
-
-```shell
-helm delete --namespace <NAMESPACE> <RELEASE-NAME>
-```
-
-Where:
-
-- `<NAMESPACE>` is the Kubernetes namespace where GitLab Runner is installed.
-- `<RELEASE-NAME>` is the name you gave the chart when installing it.
-  In the [Installing GitLab Runner using the Helm Chart](#installing-gitlab-runner-using-the-helm-chart) section, we called it `gitlab-runner`.