When enable daemon memory killer, old memory killer will be disabled

The daemon memory killer(Gitlab::SidekiqDaemon::MemoryKiller)
 - is to replace existing Gitlab::SidekiqMiddleware::MemoryKiller
 - allows Sidekiq memory balloon reasonably, within given time limit
 - reduces monitoring overhead(when there are many small jobs)
 - monitors Sidekiq memory timely(for long running jobs)
 - respects Worker sidekiq_options `memory_killer_memory_growth_kb`
 - respects Worker sidekiq_options `max_memory_killer_memory_growth_kb`

 Update document on Sidekiq memory killer ENV variables

Ignore support_bot column in users table

Closes #67295

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

Refactor protected branch resource and spec

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

Enable serving static objects from an external storage

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

CE backport for gitlab-org/gitlab-ee!14664: Show indicator to Pipelines for merge train

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

Update feature flag name for Cycle Analytics

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

https://gitlab.com/gitlab-org/gitlab-ee/issues/14671

Resolve "Snippet title whitespace"

Closes #67248

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

Add source and merge_request fields to pipeline event webhook

Closes #63338

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

Update documentation for GitHub integration

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

Update docs to reflect the new default behavior
for status check names

Use `ChronicDuration` in a thread-safe way

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

Replace 'chronic_duration' to 'gitlab_chronic_duration', to make
relevant method calls thread-safe.

https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/32554 removed the
support_bot column, but nodes were not told to ignore this column.
As a result, after the post-deploy migration ran, nodes attempted
to use this column, causing 500 errors.

Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/67295

Fix review pipeline needs blocking scheduled deploys

Closes #26893 and gitlab-ee#26893

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

Add missing `render_gfm` import to files

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

Replacing vue-resource with axios in Markdown field

Closes #61385

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

Add webpack memory test to CI

Closes #65698

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

Add rake task `db:obsolete_ignored_columns`

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

Show a list of obsolete `ignored_columns`

Back port changes for country list Api

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

Backport changes for 16252 in EE add current_user to report comparison services

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

Add missing Vue.use(Vuex) in test

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

Disable "transfer group" button when no parent group is selected

Closes #64799

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

Refactor project_edit.js to be reusable for this purpose

Closes #64799

Update Prometheus set up steps

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

Add support for custom domains to the Pages internal API

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

Add 30 and 60 minute buckets

Closes #67218

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

Port CE: Migrate discussion_ids on promoted epics

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

Notes on epics promoted from an issue used to get same discussion_id
as the notes from the issue the epic was promoted from, which would
cause problems when trying to reply to the epic discussion.