Fix failing CI/CD add/remove variable test

Closes #214910

See merge request gitlab-org/gitlab!29848

Follow-up from "Update doc/development/query_recorder.md"

Closes #210077

See merge request gitlab-org/gitlab!29532

Combine frontend and backend docs into snowplow doc

See merge request gitlab-org/gitlab!28630

This change combines backend tracking into snowplow

Update API settings document with new Elasticsearch configurations

Closes #214589 and #214591

See merge request gitlab-org/gitlab!29728

fixed two typos

See merge request gitlab-org/gitlab!29850

fix exists to exist

See merge request gitlab-org/gitlab!29849

fixed resources to resource

See merge request gitlab-org/gitlab!29851

The selector name was wrong, causing the QA smoke test to fali.

Closes https://gitlab.com/gitlab-org/gitlab/-/issues/214910

Remove feature flag for using dashboard CTE

See merge request gitlab-org/gitlab!29843

This has been running in production for a few months now without issues,
so we should be able to remove it now.

Fix Status Page active status and remove unused StatusPageSetting

See merge request gitlab-org/gitlab!29836

Resolve "Failing spec ee/spec/requests/api/group_milestones_spec.rb"

Closes #214891

See merge request gitlab-org/gitlab!29841

Docs: update links to use standard style

See merge request gitlab-org/gitlab!29837

GitLab style disallows the use of reference-style links.

Docs: Removed reflinks

See merge request gitlab-org/gitlab!29840

Related to https://gitlab.com/gitlab-org/gitlab/-/issues/212770

Remove milestones_in_roadmap feature flag

See merge request gitlab-org/gitlab!29641

In
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/28966
we've removed the beta feature flag to make Status Page
generally available.

Thereafter, in
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/29655
we've moved StatusPageSetting to StatusPage::ProjectSetting.

Apparently, we've missed to remove this model and just added
`StatusPage::ProjectSetting`.

Addionally, due to a wrong resolution of a merge conflict we've
added back the beta feature flag to the new model
StatusPage::ProjectSetting. This made the Status Page setting page
behave weirdly: It showed up but users weren't able to activate.

This commits fixes both issues:
* Remove unused StatusPageSetting model
* Remove beta feature flag from StatusPage::ProjectSetting

Fix typos in offline doc for DS

See merge request gitlab-org/gitlab!29749

- Add link to ds instructions from main offline doc
- Add maven variable to ds instruction

Docs: Removed ref links

## What does this MR do?

Removes ref links because we are switching to inline links.

## Related issues

Related to: https://gitlab.com/gitlab-org/gitlab/-/issues/212770

## Author's checklist

- [x] Follow the [Documentation Guidelines](https://docs.gitlab.com/ee/development/documentation/) and [Style Guide](https://docs.gitlab.com/ee/development/documentation/styleguide.html).
- [x] If applicable, update the [permissions table](https://docs.gitlab.com/ee/user/permissions.html).
- [x] Link docs to and from the higher-level index page, plus other related docs where helpful.
- [x] Apply the ~documentation label.

## Review checklist

All reviewers can help ensure accuracy, clarity, completeness, and adherence to the [Documentation Guidelines](https://docs.gitlab.com/ee/development/documentation/) and [Style Guide](https://docs.gitlab.com/ee/development/documentation/styleguide.html).

**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](https://about.gitlab.com/handbook/product/categories/#devops-stages).

**3. Maintainer**

1. [ ] Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review.
1. [ ] Ensure a release milestone is set.
1. [ ] If there has not been a technical writer review, [create an issue for one using the Doc Review template](https://gitlab.com/gitlab-org/gitlab/issues/new?issuable_template=Doc%20Review).

See merge request gitlab-org/gitlab!29832

Removed ref links

See merge request gitlab-org/gitlab!29827