Calling `finder.execute.count` twice will perform two queries, but these are all
in the same file, so it's easy to just reuse them.

Add option to disable commit stats to commit API

Closes #41681

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

Fix: remove unnecessary line

Closes #41501

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

Backport authorized_keys

Closes gitlab-ee#3953

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

Fixing re-ordering of an issue when dragging it to the bottom a long issue list in the board

Closes #36906

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

Remove preview_markdown from the global obj

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

Resolve "Pipeline graph uses inconsistent colors for its legend and its content"

Closes #41404

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

Backport "Fix environment scope regex" to CE

Closes gitlab-ee#4308

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

Save user ID and username in Grape API log (api_json.log)

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

Resolve "Install dev dependencies as devDependencies instead of dependencies"

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

This will enable admins to identify who actually made the API request.

Relates to #36960

Improve table pagination spec

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

Resolve "Timeout is not set for gitaly fetch_remote calls"

Closes #41683

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

Refactor dashboard todos inside dispatcher

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

The spec for "#add_key does nothing" would always have passed,
since the expectation was on both the wrong object and message.

Originally from branch 'fix-authorized-keys-enabled-default-2738' via merge request https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/2240

Removed background migrations which were intended to fix state after using Gitlab
without a default having been set

Squashed commits:
Locally, if Spring was not restarted, `current_application_settings` was still cached, which prevented the migration from editing the file. This will also ensure that any app server somehow hitting old cache data will properly default this setting regardless.
Retroactively fix migration
  This allows us to identify customers who ran the broken migration. Their `authorized_keys_enabled` column does not have a default at this point.
  We will fix the column after we fix the `authorized_keys` file.
Fix authorized_keys file if needed
Add default to authorized_keys_enabled setting
  Reminder: The original migration was fixed retroactively a few commits ago, so people who did not ever run GitLab 9.3.0 already have a column that defaults to true and disallows nulls. I have tested on PostgreSQL and MySQL that it is safe to run this migration regardless.
  Affected customers who did run 9.3.0 are the ones who need this migration to fix the authorized_keys_enabled column.
  The reason for the retroactive fix plus this migration is that it allows us to run a migration in between to fix the authorized_keys file only for those who ran 9.3.0.
Tweaks to address feedback
Extract work into background migration
Move batch-add-logic to background migration
  Do the work synchronously to avoid multiple workers attempting to add batches of keys at the same time.
  Also, make the delete portion wait until after adding is done.
Do read and delete work in background migration
Fix Rubocop offenses
Add changelog entry
Inform the user of actions taken or not taken
Prevent unnecessary `select`s and `remove_key`s
Add logs for action taken
Fix optimization
Reuse `Gitlab::ShellAdapter`
Guarantee the earliest key
Fix migration spec for MySQL

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

Backported as part of authorized_keys in https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/16014

Backport to CE, originally branch 'evn-ssh-clarify-docs

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

Originally branch 'mk-toggle-writing-to-auth-keys-1631'

See merge request !2004

Squashed commits:
Add authorized_keys_enabled to Application Settings
Ensure default settings are exposed in UI
Without this change, `authorized_keys_enabled` is unchecked when it is nil, even if it should be checked by default.
Add “Speed up SSH operations” documentation
Clarify the reasons for disabling writes
Add "How to go back" section
Tweak copy
Update Application Setting screenshot

Add find key by base64 key or fingerprint to the internal API

See merge request !250

Squashed changes:
Add unique index to fingerprint
Add new index to schema
Add internal api to get ssh key by fingerprint
Change API endpoint to authorized_keys
Add InsecureKeyFingerprint that calculates the fingerprint without shelling out
Add require for gitlab key fingerprint
Remove uniqueness of fingerprint index
Remove unique option from migration
Fix spec style in fingerprint test
Fix rubocop complain
Extract insecure key fingerprint to separate file
Change migration to support building index concurrently
Remove those hideous tabs

Make tasklist:changed test in merge_request_spec.js async

Closes #34649

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

Remove unnecessary queries on Merge Request Metrics population scheduler

Closes gitlab-org/release/tasks#13

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

Fix dashboard projects nav links height

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

Fix Webpack config for ConcatenatedModule

Closes #41649

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

Remove unnecessary dashboard scroll

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

Substitute ui_charcoal theme deprecated by GitLab Theme (10.0) with ui_indigo

Closes #41744

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