In order for frontend to display appropriate messages on why
a suggestion can't be applied, it needs to know the reason.

A new `inapplicable_reason` property is introduced and included in
the API response to achieve that. It is based on the checks to
determine whether a suggestion can be applied.

The following reasons are:

- "You don't have write access to the source branch." - when user
  has no write access to branch.
- "This merge request was merged. To apply this suggestion, edit
  this file directly." - when MR was merged.
- "This merge request is closed. To apply this suggestion, edit
  this file directly." - when MR is closed.
- "Can't apply as the source branch was deleted." - when source
  branch is deleted.
- "Can't apply as this line was changed in a more recent version."
  - when the line where suggestion is on is outdated.
- "Can't apply as these lines were changed in a more recent
  version." - when lines where suggestion is on are outdated.
- "This suggestion already matches its content." - when suggestion
  has the same content as the line it is on.
- "Can't apply this suggestion." - default message when suggestion
  cannot be applied but doesn't fall into any of criteria above.
  We won't show this message anywhere right now but it makes sense
  to return something (e.g. when suggestion is already applied).

Move note about auto stop limitations out of example

See merge request gitlab-org/gitlab!35934

Fix configuring dynamic environments sections

See merge request gitlab-org/gitlab!35923

Provide more realistic environment:action example

See merge request gitlab-org/gitlab!35935

Correct when delete environments through the UI added

See merge request gitlab-org/gitlab!35933

Fix error 500s creating new projects due to empty weights

Closes #225203

See merge request gitlab-org/gitlab!35829

Change the project_id index to be unique on vulnerability_statistics

See merge request gitlab-org/gitlab!35861

Fix existing repository_storages_weighted migrations

Closes #225588

See merge request gitlab-org/gitlab!35814

GitLab 13.1.0 added the
`application_settings.repository_storages_weighted` column, but it was
possible that the value was not seeded properly due to a stale schema
cache due to the use of ActiveRecord inside the migrations. Admins that
upgraded might see 500 errors when creating projects.

To ensure that the data is seeded properly, we surgically add a
migration that seeds the data only if it is not present. The schema
version was intentionally used to avoid backporting conflicts and to
ensure any background migrations will have the correct data when they
run. The changes were largely taken from
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/35814.

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

Fix file permissions

See merge request gitlab-org/gitlab!35880

Resolve "Need a way to ensure all newly created paid groups are indexed"

See merge request gitlab-org/gitlab!35172

Create a new ElasticsearchIndexedNamespace object
when GitlabSubscription objects are created/updated
to paid, hosted plans. Trials are not included but
will be indexed if updated to a non-trial paid plan.

Fix note formatting

See merge request gitlab-org/gitlab!35918

Clarify Gitaly mixed configuration details

See merge request gitlab-org/gitlab!35717

Edit ordering_table_columns.md, move important info first

See merge request gitlab-org/gitlab!35811

Merge branch 'mwaw/208224-move-cluster-health-feature-into-gitlab-core-BE-prometheus-proxy' into 'master'

Extract Metrics Prometheus API proxy logic into shared module

See merge request gitlab-org/gitlab!35606

Documentation: Add note about executor for managed cluster apps

See merge request gitlab-org/gitlab!35906

Remove users.ghost ignore statement

Closes #219004

See merge request gitlab-org/gitlab!35621

Stop writing to update_at on audit_events

See merge request gitlab-org/gitlab!35697

Update Auto DevOps auto-build-image to v0.3.0

See merge request gitlab-org/gitlab!35662

Adds the ability to override the default Dockerfile path via the
DOCKERFILE_PATH CI variable.

- Upstream change: https://gitlab.com/gitlab-org/cluster-integration/auto-build-image/-/merge_requests/47
- Feature request: https://gitlab.com/gitlab-org/gitlab/-/issues/212211

Don't error on wrong MR IID in changelog for cherry pick MRs

See merge request gitlab-org/gitlab!35252

Docs: tone and style edits

See merge request gitlab-org/gitlab!35809

Touching up the pages to bring them closer to GitLab standards.

For instances that upgraded to GitLab 13.1.x, it's likely that the
`application_settings.repository_storages_weighted` column did not
properly update. This happened because the schema for
`ApplicationSetting` may have been cached, so the newly-added column
wasn't visible to the model.

To ensure the column always has the right data, we make the
pre-deployment migration fill in the right data and flush the
cache. This essentially does the same thing as the post-deployment
migration, but it ensures that the application can properly run before
post-deployment migrations have completed.

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

Revert "Merge branch 'add-bin-feature-flag' into 'introduce-feature-flag-definition'"

See merge request gitlab-org/gitlab!35910

Specify "immediate parent group" as appropriate

Closes gitlab-org/manage/general-discussion#15798

See merge request gitlab-org/gitlab!35461

This reverts merge request !35540

Update ListService to use Alert Management Alerts for last_firing_events

See merge request gitlab-org/gitlab!35482