Merge branch 'docs-matrix-runner-tags' into 'master'

Crosslink parallel matrix and tags docs

See merge request gitlab-org/gitlab!79308

doc/ci/jobs/job_control.md

@@ -704,9 +704,12 @@ deploystacks: [gcp, data]
 deploystacks: [vultr, data]
 ```
 
-In [GitLab 14.1 and later](https://gitlab.com/gitlab-org/gitlab/-/issues/239737), you can
-use the variables defined in `parallel: matrix` with the [`tags`](../yaml/index.md#tags) keyword for
-dynamic runner selection.
+### Select different runner tags for each parallel matrix job
+
+> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/239737) in GitLab 14.1.
+
+You can use variables defined in `parallel: matrix` with the [`tags`](../yaml/index.md#tags)
+keyword for dynamic runner selection:
 
 ```yaml
 deploystacks:

doc/ci/yaml/index.md

@@ -2660,6 +2660,7 @@ deploystacks: [vultr, processing]
 
 - [Run a one-dimensional matrix of parallel jobs](../jobs/job_control.md#run-a-one-dimensional-matrix-of-parallel-jobs).
 - [Run a matrix of triggered parallel jobs](../jobs/job_control.md#run-a-matrix-of-parallel-trigger-jobs).
+- [Select different runner tags for each parallel matrix job](../jobs/job_control.md#select-different-runner-tags-for-each-parallel-matrix-job).
 
 ### `release`
 
@@ -3575,6 +3576,7 @@ In this example, only runners with *both* the `ruby` and `postgres` tags can run
 **Related topics**:
 
 - [Use tags to control which jobs a runner can run](../runners/configure_runners.md#use-tags-to-control-which-jobs-a-runner-can-run).
+- [Select different runner tags for each parallel matrix job](../jobs/job_control.md#select-different-runner-tags-for-each-parallel-matrix-job).
 
 ### `timeout`