Resolve "Track import issues CSV usage on GitLab.com with Snowplow"

Closes #8775

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

Remove comma from issuable email

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

Fixes z-index and margins of archived alert

Closes #56019

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

Wait for Web IDE commit animation

Closes #55972

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

ActiveRecord::Migration -> ActiveRecord::Migration[5.0] for
AddAlertManagerTokenToClustersApplicationPrometheus and EnqueuePrometheusUpdates

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

Add tests for Gitlab::Vulnerabilities classes

Closes #8707

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

Improve `bin/secpick` script and add more options

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

Update Codesandbox smooshpack library

Closes #53779

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

Added feature to specify a custom Auto DevOps chart repository

Closes #55791

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

Check if specific type of background migration are done

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

Enable some frozen string in ee/lib

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

[Data migration] Sync Approver/ApproverGroup with ApprovalRule/ApprovalRuleMember

Closes #1979

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

A "click_button" event will be triggered when the import button
of the Issues import modal is clicked.

Useful for checking progress.

Caused uniqueness constraint when inserting as users

Prevents duplicated record.

Changes to Approver/ApproverGroup are reflected to rule members.

Skip syncing code rules for approver hooks
This avoids duplicated effort as it is sync by other hooks

Do no force a find by the name

Fix spec

Finding id is enough for update

This simplifies things.
And amount of projects are quite small.

It should not err.

Push 1000 jobs at a time.

This in run in bulk migration update loop,
so access can't be avoided.

Extract transaction

This speeds up migration, as previously each project has its own job,
now they can be in a batch, avoiding 2 minutes wait interval per job.

Related to removing finalize MR

Past MR's approval requirement may change if project level setting
ever changed, so finalizing a past MR won't be accurate.

If there is a need to create estimated data,
another optional migration can be implemented.

The sync_code_owners_with_approvers call uses
original implementation, as it requires full
MR implementation to compute code owners.
However the specs are copied over,
so in the future if its behavior changes,
spec failure would notify developer to copy
existing code over.