Resolves https://gitlab.com/gitlab-org/gitlab-ee/issues/14064.

On commit status creation, the controller tries to find pipeline that
matches the specified parameters. If 'ref' not is given as parameters,
'ref' will be assigned to branch name that contains 'sha' and pipeline
for 'ref' will be searched. If there is an existing pipeline for 'ref',
commit status stage is created and appended at the end of the pipeline.
Otherwise, it will create a new pipeline for 'ref'.

The above behavior is not desirable when the only pipelines available
are not for branch. One example of other 'ref' is merge request ref.
For these pipelines, the expected value of 'ref' is supposed to be the
merge request ref name. For example, merge request with ID 42 will have
/refs/merge-requests/42/head as its ref name. Thus, if there are only
pipelines for merge requests, unless we pass 'ref' explicitly, it will
create a new pipeline for the branch that contains the 'sha' instead of
adding the created stage to the existing pipeline for merge requests.

This commit change the logic so commit status can be created on any
pipelines by default. The goal can be achieved by changing the logic
when existing pipeline is searched using the given parameters. First,
if 'pipeline_id' is specified, search for pipeline that has the same id
as 'pipeline_id'. When 'pipeline_id' is not given, but 'ref' is given,
search for pipeline that has the same 'ref' and 'sha' value. Note that
'sha' will always be given. Otherwise, search the latest pipeline that
has the same 'sha', which will only returns nil if there is no pipeline
created for that particular 'sha'.

PostgreSQL support troubleshooting page

See merge request gitlab-org/gitlab!18323

Fix merge request approvals test and others

Closes #33762

See merge request gitlab-org/gitlab!18427

Previously fabricate_or_use would only create a User instance with the
provided username and password. This was fine when only those creds
were needed (e.g., to sign on), but it's not enough in tests that
need other user details, e.g., the user's name.

This changes fabricate_or_use so that it fetches the user via the API,
which provides access to the user's details.

Refactor RSpec test suite to remove duplication

See merge request gitlab-org/gitlab!18532

Fix cancel button in issue template update warning

See merge request gitlab-org/gitlab!18334

This commit also does the following:

- Adds an extra spec to validate close and
dismiss buttons
- Adds an extra assertion to validate template
warning element not found on the DOM
- Fixes resetting template content for new issues
- Fixes content saving to localStorage when
template changed

Add controller and feature flag for code analytics

See merge request gitlab-org/gitlab!17618

- Add feature flag for code analytics actions.
- Connect the controller to the real finder backend.
- Implement input parameter validation.
- Update the query to return the repository file id.

Allocate IID for deployments outside of the pipeline transaction

Closes #21518

See merge request gitlab-org/gitlab!17696

Rename Vulnerabilities to Findings in Groups security routes

See merge request gitlab-org/gitlab!17355

Add support of both /vulnerability_findings
and /vulnerabilities routes for Group
Security Dashboard, toggled by the feature
flag.

Revert "Revert multi select"

See merge request gitlab-org/gitlab!18516

Remove `depend_on_persistent_pipeline_ref` feature flag

Closes #14863

See merge request gitlab-org/gitlab!18185

Allow config Sidekiq worker memory limit in ENV

See merge request gitlab-org/gitlab!18071

Make IS_GITLAB_EE consistent

See merge request gitlab-org/gitlab!18442

Currently:
1. If `IS_GITLAB_EE=` is used, it fails to generate Webpack
   as it cannot be parsed as JSON,
2. If `IS_GITLAB_EE=1` is used, it fails on GitLab CE,
3. If `IS_GITLAB_EE=0` it does work correctly, and disables EE,
4. If `IS_GITLAB_EE=1` is used on GitLab EE it effectively required
   to run on EE changes.

This changes to:

Make `IS_GITLAB_EE=` to donate the intent to disable or enable EE
sources, instead of requiring it, and makes the check consitent
in behaviour.

Bump GITLAB_ELASTICSEARCH_INDEXER_VERSION=v1.4.0

Closes #33255 and gitlab-elasticsearch-indexer#39

See merge request gitlab-org/gitlab!18558

Enable frozen string for spec/tasks

See merge request gitlab-org/gitlab!18552

Edit new configuration settings documentation

See merge request gitlab-org/gitlab!18557

Remove ActionType constants from epic tree frontend

See merge request gitlab-org/gitlab!17971

This commit removes the FF as it's deemed stable

This commit reduces the lock contention of internal iid

Which fixes https://gitlab.com/gitlab-org/gitlab/issues/33255 and also
includes
https://gitlab.com/gitlab-org/gitlab-elasticsearch-indexer/merge_requests/39

Add more details on how to use Docker-based Gitlab with Docker-based PlantUML

See merge request gitlab-org/gitlab!18204

The MR also fixes the relative path to the PlantUML service

Fix metrics chart embed tooltip spacing

Closes #34063

See merge request gitlab-org/gitlab!18543

Operator can see all projects using an instance level cluster

See merge request gitlab-org/gitlab!18173

Refactor of appearance/customization docs

Closes #31189

See merge request gitlab-org/gitlab!18049

Move most information regarding the appearance section
to /user/admin_area, and redirect from /customization.
Updates screenshots, information, process, etc.

Fixed cert-manager retry logic to apply correct exit code

Closes #34065

See merge request gitlab-org/gitlab!18545

Partially addresses:

https://gitlab.com/gitlab-org/gitlab/issues/27703

Enable frozen string for spec/uploaders

See merge request gitlab-org/gitlab!18547

Partially addresses:

https://gitlab.com/gitlab-org/gitlab/issues/27703

Update Auto DevOps quickstart

Closes #33075

See merge request gitlab-org/gitlab!18356

Update guide to show new base domain loc, update images