Add container registry to object storage

See merge request gitlab-org/gitlab!71905

Add primary email to emails upon confirmation

See merge request gitlab-org/gitlab!70872

Fix merge request commits that are missing committer/author details

See merge request gitlab-org/gitlab!73307

Update user attributes for Group SAML enterprise users

See merge request gitlab-org/gitlab!72792

Consolidate the logic for SAST prompt experiment

See merge request gitlab-org/gitlab!73034

Filter Dast Profiles with Schedule

See merge request gitlab-org/gitlab!72301

Improve error tracking error handling

See merge request gitlab-org/gitlab!73557

In MR https://gitlab.com/gitlab-org/gitlab/-/merge_requests/63669 we
introduced a new data format for storing merge request diff commit
authors and committers. As part of this work we made changes to the
import/export code to support this new format, and added a set of
migrations to migrate existing data to this new format. At this time we
supported reading and writing of data in both the old and new format,
allowing us to gradually migrate data over to the new format.

In https://gitlab.com/gitlab-org/gitlab/-/merge_requests/72219 we
ensured all migrations are done, stopped using the old data format, and
removed the columns storing this data.

Unfortunately, this chain of events uncovered a bug in our import/export
logic. Consider the following timeline of events:

1. You export project "Cooking Recipes" from a GitLab instance running a
   version earlier than 14.1 (e.g. 14.0).
2. The instance you intend to import this project into is running 14.1
   or newer. Existing data has been fully migrated already.
3. You import the project into this new instance.

At this point, the imported data is using the old format, not the
format. This is because we forgot to take into account users importing
exports using GitLab 14.0 or older, instead only covering exports
generated using GitLab 14.1 or newer. Because the background migrations
finished, or the data imported would fall in a "bucket" (= a chunk or
rows to migrate) that had already been migrated, the data would never be
updated to the new format.

In this commit we resolve this problem in two steps. First, we change
the import/export logic to support importing data in both the old and
new format. Exports still use the new format. In addition, we include a
background migration that processes all projects created using a GitLab
import/export since the first mentioned merge request was introduced.
For each such project we scan over the merge request diff commits and
fix any that are missing the commit author or committer details.

For small self-hosted instances this process is unlikely to take more
than a few minutes. On GitLab.com however we expect this process to take
a few days, as we have to process around 200 000 projects imported since
July. This means we'll likely need additional manual intervention
similar to the manual work needed for
https://gitlab.com/gitlab-org/gitlab/-/issues/334394.

See https://gitlab.com/gitlab-org/gitlab/-/issues/344080 for additional
details.

Changelog: fixed

Redirected topic that was viewed infrequently

See merge request gitlab-org/gitlab!73684

Cross link cascade feature section and rename section

See merge request gitlab-org/gitlab!73238

Fix: update broken pipeline layout

See merge request gitlab-org/gitlab!73477

Fix broken layout for
Web IDE and the pipelines
list inside the code_quality_walkthrough
experiment.

Changelog: fixed

Make previous test detection work for other projects and hosts

See merge request gitlab-org/gitlab!73160

Add new environment folder component

See merge request gitlab-org/gitlab!73487

[ci skip]

Update group migration doc feature flag info

See merge request gitlab-org/gitlab!73500

Fix examples for rake import commands

See merge request gitlab-org/gitlab!73632

Fix Rails/SaveBang RuboCop offenses for spec/models

See merge request gitlab-org/gitlab!73494

Add external_issue_alert component to Jira / ZenTao issue details page

See merge request gitlab-org/gitlab!73444

To be used by both the Jira and ZenTao integrations

Fix board scope issue when issue_boards_filtered_search is enabled

See merge request gitlab-org/gitlab!73008

Revise extension page title for accuracy

See merge request gitlab-org/gitlab!73663

Update Feature proposal - detailed.md

See merge request gitlab-org/gitlab!73678

Add project count and coverage count to tooltip

See merge request gitlab-org/gitlab!73215

CI lint: add include_jobs field to api endpoints

See merge request gitlab-org/gitlab!72539

Merge branch '324623-clarify-and-document-usage-of-wau-acronym-in-metrics-definitions' into 'master'

Add definition for WAU and MAU to Service Ping page

See merge request gitlab-org/gitlab!73282

Edit steps for Teams integration

See merge request gitlab-org/gitlab!73657

Edits to Admin Area settings page

See merge request gitlab-org/gitlab!73211