Remove two older and not-recommended migration helpers which use
background migrations to rename or change type of a column. Generally we
prefer to use a custom BG migration for the time being, since these
migration helpers have a few issues with their implementation.

These migration helpers are also a good candidate to be reimplemented
using batched background migrations, following current "best practices."

Add GraphQL mutation to revoke an agent token

See merge request gitlab-org/gitlab!77635

Added Storybook stories for shared survey Banner

See merge request gitlab-org/gitlab!77655

Remove log_implicit_sidekiq_status_calls feature flag

See merge request gitlab-org/gitlab!77349

Update translation levels - Jan 2022

See merge request gitlab-org/gitlab!77694

Set low custom apdex for Value Stream Analytics

See merge request gitlab-org/gitlab!74845

Add the CI/CD data time-decay blueprint

See merge request gitlab-org/gitlab!70052

Also add a few more minor changes

This commit also assigns and AEC and a domain expert.

Move files from ~/ to more approprate modules

See merge request gitlab-org/gitlab!77704

Value Stream Analytics is a data-intensive feature that users do not
expect to load as quickly as other resources. This sets a custom
apdex SLI urgency of "low" to allow for the feature's historically
relatively slower load times.

Pass formats explicitly when rendering .md file

See merge request gitlab-org/gitlab!75778

New Crowdin translations - 06 January 2022

See merge request gitlab-org/gitlab!77680

[skip ci]

Remove foreign key constraint ci_pending_builds.namespace_id

See merge request gitlab-org/gitlab!77724

Followed users events (filter ALL) should be ordered by id DESC

See merge request gitlab-org/gitlab!77436

The events finder should sort
followed users events by id DESC.

This behavior was broken by the merge request
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/77028.

Changelog: changed

Move files from ~/ to more approprate modules

See merge request gitlab-org/gitlab!77708

The loose foreign key was already added for this in
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/77636 .  We've
confirmed in https://gitlab.com/gitlab-org/gitlab/-/issues/348269 that
it is indeed safe to swap these foreign keys for loose foreign keys.

Changelog: other

Fix sticky filters not working on vulnerability report

See merge request gitlab-org/gitlab!77647

Update snippet search badge to use pajamas

See merge request gitlab-org/gitlab!77726

Update Gitaly version

See merge request gitlab-org/gitlab!77742

Remove :operational_vulnerabilities feature flag

See merge request gitlab-org/gitlab!77639

Quarantine highly flaky spec

See merge request gitlab-org/gitlab!77739

Clean up table in variables doc

See merge request gitlab-org/gitlab!77740

Add deprecation notice to Pseudonymizer documentation

See merge request gitlab-org/gitlab!77582

Sort the table, and make sure the definition column
only has one keyword per row. Splits two rows into
3 each as a result, so each keyword has its own row

https://gitlab.com/gitlab-org/gitlab/-/issues/349762

Document that variables can be expanded in `tags:`

See merge request gitlab-org/gitlab!77484