Merge branch '8891-table-headers-font-size-is-too-big-in-group-level-security-dashboard' into 'master'

Fix Security Dashboard Header fontsize

Closes #8891

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

Support new report syntax for common vulnerabilities (CE backport)

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

Support new syntax for common vulnerabilities

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

Update serverless extension to yml

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

Fixes broken link

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

Fix deprecation: returning false in Active Record and Active Model callbacks

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

fix border-radius for related issues

Closes #8963

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

This MR also removes other reports and uses one common set of fixtures
for all test types.

Add project code view permissions

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

Add project code view permissions

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

Don't ignore conflicts in db/schema.rb

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

Expose `CI_API_V4_URL` CI/CD variable

Closes #54621

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

Improve documentation about only except default values

Closes #55699

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

EE: Merge branch 'ac-releases-api-with-assets' into 'master'

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

Add filtering for history and summary on security dashboard

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

Adds basic filtering to the Group Security Dashboard frontend

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

The new reports are always a top-level Hash with explicit `version:`
field. Old reports that are Arrays are converted to Hash representation
with indication what version is being used.

This MR also removes other reports and uses one common set of fixtures
for all test types.

Include templates

Closes #53445

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

It's not entirely clear to me why we were ignoring db/schema.rb in the
first place, but this should not be done now that we merge CE into EE
automatically. Doing so can lead to changes being thrown away in the
event of a conflict, which can then lead to EE pipelines failing.

Don't ingore the `gitlab.pot` in ee_compat_check

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

Add missing externalized strings

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

Merge branch '4553-geo-hashed-storage-migration-failure-does-not-log-to-sentry-or-geo-log-well' into 'master'

Improve error handling when namespace cannot be moved

Closes #4553

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

Guarantee visually correct order of runners on the "Admin Area > Runners" page

Closes #49791

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

Support asset links creation in `POST /projects/:id/release`

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

Documentation for Release page MVC

Closes #41766

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

If there are new strings in CE, they need to be added to EE
manually. As the `locale/gitlab.pot` file can't be merged
automatically during the upstream merge.