In some conditions - the most trivial of which are when this spec is run
in isolation with a clean test database - the profile schedule and
profile created by this spec could have the same ID, in different
tables. The spec would then find the wrong audit event in the audit
events table, because it was looking up only by `target_id`, and fail as
a result.

Fix re-use of extensions between instances

See merge request gitlab-org/gitlab!77319

Changelog: fixed

Fix Gitlab/DelegatePredicateMethods offenses

See merge request gitlab-org/gitlab!76001

E2E: Validate merge request comments are migrated

See merge request gitlab-org/gitlab!77170

Adds workItemCreate mutation to the GraphQL API

See merge request gitlab-org/gitlab!76401

Adjusts pending members to be distinct

See merge request gitlab-org/gitlab!76864

Adding more loose foreign keys for ci_pipelines from merge_requests, vulnerability_statistics, vulnerability_occurrence_pipelines

See merge request gitlab-org/gitlab!77323

Update security configuration tabs to utilize lazy loading

See merge request gitlab-org/gitlab!77280

Fix `add-jh-folder` where to move the folder

See merge request gitlab-org/gitlab!77309

Stub rate limiting logic in raw_controller_spec

See merge request gitlab-org/gitlab!77105

Fix filename is overflowing modal when importing

See merge request gitlab-org/gitlab!75891

Merge branch '344382-make-badges-in-ee-app-views-projects-mirrors-_table_pull_row-html-haml-pajamas-compliant' into 'master'

Make badge in mirrors/_table_pull_row partial Pajamas-compliant

See merge request gitlab-org/gitlab!77100

Create a unique group for minimal access specs

See merge request gitlab-org/gitlab!77290

Allow for consolidated edit button in E2Es

See merge request gitlab-org/gitlab!77216

Add toggle method to control use_minimum_char_limit

See merge request gitlab-org/gitlab!76835

Add section description to security training configuration

See merge request gitlab-org/gitlab!77173

These [loose foreign
keys](https://docs.gitlab.com/ee/development/database/loose_foreign_keys.html)
are the first step to removing the cross-database foreign keys between
`main` and `ci` databases.

These 3 foreign keys have been determined to be safe for swapping to
loose foreign keys per
https://gitlab.com/gitlab-org/gitlab/-/issues/348269 .

These Loose foreign keys do not require any tests yet until we actually
remove the foreign key as we can't validate the behaviour if the real
foreign key already does the cleanup for us and we already have a test
to show that deletes to `ci_pipelines` are tracked.

Fix Rails/SaveBang offenses

See merge request gitlab-org/gitlab!75894

Delete events in batches when project is destroyed

See merge request gitlab-org/gitlab!77031

Add group crm settings

See merge request gitlab-org/gitlab!76983

Clarify deprecation DRI is EM or PM

See merge request gitlab-org/gitlab!77252

Remove sbt from license compliance docs

See merge request gitlab-org/gitlab!77295

Update push mirroring page

See merge request gitlab-org/gitlab!76199

Remove OAuth paths from protected paths rate limit

See merge request gitlab-org/gitlab!76882

Add Staging Canary and Staging Ref to QA metrics

See merge request gitlab-org/gitlab!77237

Export Project LFS Objects as part of GitLab Migration

See merge request gitlab-org/gitlab!77018

Remove find_tag_via_gitaly feature flag

See merge request gitlab-org/gitlab!77303