Rails silently casts NULL `lock_version` values to 0 while doing
optimistic locking, which causes false stale object exceptions. We had a
monkey patch that would change it to check for [NULL, 0] but want to
avoid monkey-patching if possible, which means we need to clean up our
database values.

This commit deals with Issuables (Issues, Epics, Merge Requests)

Separate 4 EE entities into own class files

See merge request gitlab-org/gitlab!25400

Migrated mutations_spec for jest

See merge request gitlab-org/gitlab!25379

Add scheduling_type to tags entry with default values

Closes #207266

See merge request gitlab-org/gitlab!25545

Cleanup labels helper and fix prepending logic

See merge request gitlab-org/gitlab!25257

Merge branch '207195-move-the-vulnerability-status-dropdown-from-the-dashboard-to-the-vulnerabilities-path' into 'master'

Merge the vulnerability state dropdown into existing page

See merge request gitlab-org/gitlab!25498

Merges the vulnerability dropdown into an existing page that was
created after the vulnerability dropdown feature was implemented
and deletes the files from the old location

This makes it easier to override this helper's
class methods in EE

Introduce `idempotent` worker attribute with new Cop

See merge request gitlab-org/gitlab!25202

- Fixes https://gitlab.com/gitlab-org/gitlab/issues/207266

Migrate fa-spinner to spinner in views dashboard todos.

See merge request gitlab-org/gitlab!25142

Remove unused reload property from board_store

See merge request gitlab-org/gitlab!25490

Create ResourceMilestoneEvents whenever milestones are changed

See merge request gitlab-org/gitlab!24780

Rescue elasticsearch server error in pod logs

See merge request gitlab-org/gitlab!25367

Add context to background migrations

See merge request gitlab-org/gitlab!25008

This will add the `caller_id` to the context for every job that might
be scheduled from a background migration. So if a background migration
reschedules itself or another migration, this will now be visible in
the metadata.

Remove jira_connect_app feature flag

See merge request gitlab-org/gitlab!24818

Removing the :jira_connect_app
feature flag from controllers, services
and specs

Fixes 'tags' support in 'default'

See merge request gitlab-org/gitlab!24741

Fix feature flag check on container registry explorer

Closes #23315

See merge request gitlab-org/gitlab!25511

Chore: replace underscore with lodash for in /app/assets/javascripts/blob

See merge request gitlab-org/gitlab!25113

Consider flags disabled when generating GraphQL schema

See merge request gitlab-org/gitlab!25172

Use default system note content for MilestoneNote

Also update specs and fixed one typo.

Remove milestones_of method

Fix display of synthetic milestone notes

Fix display of synthetic milestone notes with direct banzai render call

Cleanup and simplify options hash

Extract ResourceEventTools module

Move some scopes and validations to resource events module

Add changelog entry

Use sentinel value for truncated param logging

See merge request gitlab-org/gitlab!25518

Remove ignore_column :storage_version

Closes #205196

See merge request gitlab-org/gitlab!25515

Add http status cop to some subdir request specs

See merge request gitlab-org/gitlab!25166

285 files inspected, 21 offenses detected, 21 offenses corrected

Our Elasticsearch mapping on GitLab.com requires params to be an array
of hashes, each hash with a `key` and `value` key. This does not apply
to our Sidekiq arguments logging, as Sidekiq arguments can be of
different types anyway, and do not have keys.

Being collecting blob size metrics

See merge request gitlab-org/gitlab!25462

Use gitlab-workhorse v8.22.0

See merge request gitlab-org/gitlab!25425

This might have done something once but it doesn't anymore

Resolve "Migrate '.fa-spinner' to '.spinner' for 'app/assets/javascripts/blob/template_selector.js'"

See merge request gitlab-org/gitlab!25045