Docs: Fix anchors related to variables doc (!27081) · Merge requests · GitLab.org / GitLab FOSS

The source project of this merge request has been removed.

What does this MR do?

This fixes the anchor links broken when headings were changed in https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/26336, and removes the manual anchors which are no longer needed as all anchors point to the correct headings now.

Old	New
`#variables`	`#gitlab-cicd-environment-variables`
`#variables-expressions`	`#environment-variables-expressions`
`#syntax-of-variables-in-job-scripts`	`#syntax-of-environment-variables-in-job-scripts`
`#group-level-variables`	`#group-level-environment-variables`
`#priority-of-variables`	`#priority-of-environment-variables`
`#protected-variables`	`#protected-environment-variables`
`#deployment-variables`	`#deployment-environment-variables`

Follow the Documentation Guidelines and Style Guide.
Link docs to and from the higher-level index page, plus other related docs where helpful.
Apply the ~Documentation label.

All reviewers can help ensure accuracy, clarity, completeness, and adherence to the Documentation Guidelines and Style Guide.

1. Primary Reviewer

Review by a code reviewer or other selected colleague to confirm accuracy, clarity, and completeness. This can be skipped for minor fixes without substantive content changes.

2. Technical Writer

Optional: Technical writer review. If not requested for this MR, must be scheduled post-merge. To request for this MR, assign the writer listed for the applicable DevOps stage.

3. Maintainer

Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review.
Ensure a release milestone is set and that you merge the equivalent EE MR before the CE MR if both exist.
If there has not been a technical writer review, create an issue for one using the Doc Review template.

Edited Apr 08, 2019 by Achilleas Pipinellis