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

Enable quarantined service ping metrics

See merge request gitlab-org/gitlab!73348

Add reCAPTCHA to password reset and confirmation email forms

See merge request gitlab-org/gitlab!72331

Resolve "Gitlab::ApplicationRateLimiter.throttled? key _must_ be a symbol"

See merge request gitlab-org/gitlab!73440

Quarantine flaky user assigns self spec

See merge request gitlab-org/gitlab!73355

Ensure specs are under saas context when needed

See merge request gitlab-org/gitlab!72856

Implement loading and error state in DAST scans view

See merge request gitlab-org/gitlab!72994

Use GlAvatar in approval rule selector

See merge request gitlab-org/gitlab!73334

Change additional_snowplow_tracking feature flag type to Ops

See merge request gitlab-org/gitlab!73434

Make breadcrumb toggle inline

See merge request gitlab-org/gitlab!72754

Fix the offences introduced by Performance/OpenStruct

See merge request gitlab-org/gitlab!70900

Exclude project namespaces from namespace#search

See merge request gitlab-org/gitlab!73421

Default feature labels on feature flag roll-out issue

See merge request gitlab-org/gitlab!73513

Fix Feature Category in Tags Controller

See merge request gitlab-org/gitlab!73525

This commit fixes that the specific endpoint
on tags controller is categorized in source code management.

Add better error handling to BulkImports::GroupLoader

See merge request gitlab-org/gitlab!73191

Add documentation on test dependency across backend and frontend

See merge request gitlab-org/gitlab!73448

When searching namespces by path or name we are not expecting
to get ProjectNamespaces in results yet, so we need to filter
those out for now.

Remove temporary invite member cookie transfer method

See merge request gitlab-org/gitlab!73475

Run experiment on New Board CTA

See merge request gitlab-org/gitlab!72683

[VSA] Hide warning banner when navigating away

See merge request gitlab-org/gitlab!73527

Pluralize DevOps Report to DevOps Reports in UI

See merge request gitlab-org/gitlab!73319

Doc | Improving firewall rules for Geo

See merge request gitlab-org/gitlab!73445

Refactor specs prevent_cross_database_modification_spec

See merge request gitlab-org/gitlab!73451

Exclude project namespaces from autocomplete routes finder

See merge request gitlab-org/gitlab!72862

DevOps Report (singular) actually refers to 2 features. That has caused
confusion. This changes it to be DevOps Reports (plural) in the UI, to
indicate it is a category. This aligns the app with the marketing
content, which already uses the plural version.

This also fixes some references to DevOps Report that should be
references to DevOps Adoption or DevOps Score.

Changelog: changed

Improve Pages CI/CD instructions

See merge request gitlab-org/gitlab!73452

Crosslink Puma docs

See merge request gitlab-org/gitlab!73489

Refactor labels selector in board scope

See merge request gitlab-org/gitlab!71983

Some time ago we made all specs default to preventing cross database
modification. Thus the `prevent_cross_database_modification` tag was
unecessary. This meant slightly re-organising the tests and removing 1
redundant test and re-writing one test slightly since it wasn't covered
elsewhere.

Excludes project namespaces in autocomplete routes finder.

Add note that buckets should be specified for all object types

See merge request gitlab-org/gitlab!72965

Exclude project namespace when computing subgroup counts

See merge request gitlab-org/gitlab!73305