Previously we were casting the invalid project IDs to strings because
we were trying to cover the case where the client sends an invalid ID
to the backend. This was causing problems on client application because
it was expecting the IDs to be integers. I do believe that the effort
of covering the case where client sends an invalid ID will cause more
problems than it solves therefore I am removing the related logic and
assuming the client is always sending us valid IDs.

/closes https://gitlab.com/gitlab-org/gitlab/-/issues/196729

Make Jira capitalisation consistent (user-facing)

See merge request gitlab-org/gitlab!29875

Change reference links to inline

See merge request gitlab-org/gitlab!29869

Refactor backup and restore Rake tasks page

See merge request gitlab-org/gitlab!29745

Also fixes links to renamed sections and other minor improvements.

Edits to clarify users statistics

See merge request gitlab-org/gitlab!29555

- Change from `jira` to `Jira` in UI

documentation: Add information on pinning images by digest.

See merge request gitlab-org/gitlab!24419

Refactor ProjectMembers and GroupMembers controllers

Closes #118630

See merge request gitlab-org/gitlab!29501

Refactor Ci::Processable validation specs

See merge request gitlab-org/gitlab!29626

Document SQL-based Praefect replication queue

See merge request gitlab-org/gitlab!29859

Change reference links to inline links
in various api and other docs.

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

This new configuration parameter needs to be used until we make it the
default mode. That is gated on running migrations by default:
https://gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/4033

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