Update gitlab-svg to 1.52

See merge request gitlab-org/gitlab-ce!25145

Resolve "Tool Tip Hides Menu Item"

Closes #55209

See merge request gitlab-org/gitlab-ce!24285

Adding info for the location of cicd timeout setting per project

See merge request gitlab-org/gitlab-ce!25136

Docs: add description on how to retrieve artifacts when authentication is required

See merge request gitlab-org/gitlab-ce!23197

Create the source branch for a GitHub import

Closes #57370

See merge request gitlab-org/gitlab-ce!25064

Kill all PostgreSQL connections for rake dev:setup

Closes gitlab-development-kit#450

See merge request gitlab-org/gitlab-ce!24743

Update sshkey to v2.0.0

Closes #47150

See merge request gitlab-org/gitlab-ce!25115

Stablize select_kind using retry_on_exception

Closes gitlab-org/quality/nightly#72

See merge request gitlab-org/gitlab-ce!25027

add client support for CountDivergingCommits rpc

See merge request gitlab-org/gitlab-ce!24287

When the GitHub importer creates a merge request, it retrieves the SHA
but does not actually create the source branch. This makes it impossible
to merge an open merge request, particularly if the source branch were
from a forked project. In that case, the branch will never exist because
the original `project-name:source-branch` name is never created, nor
is it a valid branch name.

To prevent possible branch name conflicts, forked source branches
are now renamed `github/fork/project-name/source-branch` and created
when necessary.

Note that we only create the source branch if the merge request
is open. For projects that have many merge requests, the project
would end up with a lot of possibly dead branches.

Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/57370

If there are any clients connected to the DB, PostgreSQL won't let you
drop the database. It's possible that Sidekiq, Unicorn, or some other
client will be hanging onto a connection, preventing the DROP DATABASE
from working. To workaround this problem, this method cancels all the
connections so that the db:reset command will work.

Note that there's still a slight possibility a client connects after its
connection is terminated. If this is an issue, we could solve it by
revoking CONNECT access, but for now it seems this works.

Closes https://gitlab.com/gitlab-org/gitlab-development-kit/issues/450

Adding convenience method to project model

See merge request gitlab-org/gitlab-ce!25108

Merge branch '57287-documentation-for-handling-more-complex-only-merge_requests-scenarios-is-sparse' into 'master'

Docs for MR pipeline rule interactions

Closes #57287

See merge request gitlab-org/gitlab-ce!24929

Fix security harness script

See merge request gitlab-org/gitlab-ce!25050

Address review comment for app/services/task_list_toggle_service.rb

Closes #57413

See merge request gitlab-org/gitlab-ce!25013

This release fixes a bug in handling certain ed25519 keys. For more
details, see this GitHub issue:

https://github.com/bensie/sshkey/issues/34

refactors the ui for diverging commits so that it's only a single
bar instead of two separate bars

Port of EE translations

See merge request gitlab-org/gitlab-ce!25100

Add HTML output example to profiling

See merge request gitlab-org/gitlab-ce!25103

Change find flags to also work with Alpine

Closes #57341

See merge request gitlab-org/gitlab-ce!25104

Resolve "Follow-up from "API group labels""

Closes #57450

See merge request gitlab-org/gitlab-ce!25070

Refactor the upgrading from source docs

Closes gitlab-org/release/framework#190

See merge request gitlab-org/gitlab-ce!25003

Update on using self-signed certs with registry

See merge request gitlab-org/gitlab-ce!25086

Fix branch API table format

Closes #57480

See merge request gitlab-org/gitlab-ce!25091

This changes the guides for upgrading from CE source to EE source so we
no longer need separate documents for every version. This removes the
need for release managers to create and update these documents, and
allows developers to add these instructions as part of their code
changes.

New Crowdin translations

See merge request gitlab-org/gitlab-ee!9510

Remove HipChat integration from GitLab

Closes #52424

See merge request gitlab-org/gitlab-ce!22223

Instead of requiring one separate document for every version (which is
created by release managers), we now use a single document for both
Community Edition and Enterprise Edition. This allows developers to add
guidelines right away, instead of release managers having to determine
what to add.

Version specific upgrading instructions are placed in a separate
section. This prevents instructions from lingering around for many
versions should a developer forget to remove them. This also ensures
that all instructions are kept in a single place, instead of being
spread across different documents.

A minor downside is that CE and EE guidelines now live in the same
document, which could cause merge conflicts. Since we are working
towards a single codebase, this should only be an issue until we merge
the codebases together; something we expect to do in the coming months.

This commit also removes all old upgrading instructions, but these can
still be accessed using Git branch specific URLs (included in the
updating README).