Expose update project service JSON endpoint

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

Utilize `json_fields` to expose fields via
`Service#as_json(only: json_fields)`.

Fix create isssue for container scanning from dashboard issue

Closes #13676

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

Add tests for checking diffent type of array

Upgrade Gitaly to v1.62.0

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

Update ExternalPullRequest on :synchronize action

Closes gitlab-ce#67191

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

Give notification buttons btn-xs class

Closes #60724

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

Merge branch '9102-hide-dismissed-vulnerabilities-in-the-group-security-dashboard-backport' into 'master'

Add toggle to show/hide dismissed vulnerabilities (ports ee!15333)

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

Add toggle to show/hide dismissed vulnerabilities

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

- Added a toggle that can be turned on to hide dismissed vulnerabilities
- Added specs for gl-toggle-vuex
- Updated specs for all changed files

Add changelog

Create issue from generic alert notification

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

In order to keep the ExternalPullRequest record in sync
with GitHub we need to update the info when any metadata
we track changes. When the source_sha changes because of
a branch push, GitHub emits the :synchronize action on
the pull_request webhook.

Improve performance and (memory usage (a little)) of project export

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

ActiveModel::Serialization is simple in that it recursively calls
`as_json` on each object to serialize everything. However, for a model
like a Project, this can generate a query for every single association,
which can add up to tens of thousands of queries and lead to memory
bloat.

To improve this, we can do several things:

1. We use `tree:` and `preload:` to automatically generate
   a list of all preloads that could be used to serialize
   objects in bulk.

2. We observe that a single project has many issues, merge requests,
   etc. Instead of serializing everything at once, which could lead to
   database timeouts and high memory usage, we take each top-level
   association and serialize the data in batches.

For example, we serialize the first 100 issues and preload all of
their associated events, notes, etc. before moving onto the next
batch. When we're done, we serialize merge requests in the same way.
We repeat this pattern for the remaining associations specified in
import_export.yml.

Resolve "Job Failed #290891184 - docs lint broken in `master`"

Closes #67209

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

Signed-off-by: Rémy Coutable <remy@rymai.me>

Docs: Clarified note for preferred integration method

Closes #28683

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

Align introduced text to standard

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

Fix capitalization of GitLab

Closes #67023

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

docs update to mysql_to_postgresql.md adding timeout parameters

Closes #43903

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

Improve performance of search by lowering counters

Closes gitlab-ee#11777

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

Lowering the limit when performing search from 1001 to 101.
This will allow us to speed this process.

Add skeleton Pages internal API

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