Bump pry-rails to 0.3.9

See merge request gitlab-org/gitlab!24151

Remove code hotspots tables

Closes #198313

See merge request gitlab-org/gitlab!23590

- Using `with_lock_retries` helper method.
- Fix duration conversion within `with_lock_retries`.

Docs: explain why mentioning tiers and versions is important

See merge request gitlab-org/gitlab!23414

Update docs ee/development/uploads

See merge request gitlab-org/gitlab!23870

Refactor ProjectMembers controller

See merge request gitlab-org/gitlab!23960

Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>

Restyle signup welcome page

See merge request gitlab-org/gitlab!23512

Fix test runtime ID not working with bin/spring

Closes #198362

See merge request gitlab-org/gitlab!23671

Do not show 'NaN files' in diff stats when a MR diff does not have any changes.

See merge request gitlab-org/gitlab!24087

Merge branch '28376-merge-request-comments-have-stopped-appearing-for-the-whole-project' into 'master'

Fix for invalid diff lines on corrupt diff notes

See merge request gitlab-org/gitlab!23786

This is to prevent many issues when rendering notes that are
corrupted in some way. There seem to be multiple bugs that
allow this to happen, and the result is that it fails to
render the entire block of notes.

Merge branch '197292-support-require_password_to_approve-in-post-projects-id-approvals-api-endpoint' into 'master'

Support require_password_to_approve in POST /projects/:id/approvals API endpoint

Closes #197292

See merge request gitlab-org/gitlab!24016

Fix applying suggestion with empty custom message

See merge request gitlab-org/gitlab!24144

The problem was that when running under `spring`, the process name is
not `rspec` anymore. I think we don't need to test
the process name anyway, we can instead rely on just `Rails.env`.

Update environments dropdown header

See merge request gitlab-org/gitlab!24096

Add retry mechanism to after import

Closes #198503

See merge request gitlab-org/gitlab!23846

Display Feature Flag Internal Ids

See merge request gitlab-org/gitlab!23914

Return feature flag internal id from backend
Remove featureFlagIid feature flag

Fix for #198353, copied and pasted markdown video/audio snippets not playable

Closes #198353

See merge request gitlab-org/gitlab!23918

Fix new MR UI not rendering commit info

See merge request gitlab-org/gitlab!24140

This change fixes showing 'NaN files' when a MR diff does
not have any changes

When the custom suggestion message is cleared,
it's stored as an empty string in db. In this case
we still need to apply default commit message

Use time ranges in date picker (utils)

See merge request gitlab-org/gitlab!23765

 - Replace expect with allow

- use import_failure_service
- add missing specs

Fix typo on serializer README.md

See merge request gitlab-org/gitlab!24105

Fix broken spec in help_controller_spec.rb

Closes #199976

See merge request gitlab-org/gitlab!24139

Allow scheduling jobs in batch with contexts

See merge request gitlab-org/gitlab!23519

This adds helper methods for the `bulk_perform_in` and
`bulk_perform_async` methods that allow specifying a context per job.

Scheduling jobs with contexts that need to be different based on the
arguments passed can be done by passing in an array of objects, and
defining how to build arguments and contexts for those objects.

For example:
      ProjectImportScheduleWorker.bulk_perform_async_with_contexts(
        projects,
        arguments_proc: -> (project) { project.id },
        context_proc: -> (project) { { project: project } }
      )

This will schedule `ProjectImportScheduleWorker` jobs called with the
project.id. And will create contexts using the project. The developers
need to make sure that the required resources for building a context
are loaded: The route and the namespace of a project.

The batch context will be stored on the worker class when scheduling
the job, so the sidekiq middleware can fetch the right context based
on those arguments and apply them to the job when scheduling it.

This also implements this method for the `UpdateAllMirrorsWorker`
which schedules `ProjectImportScheduleWorker` in batch. When adding
this, the `ProjectImportScheduleWorker`-jobs will have a context.

Fix spec so that it does not depend on spec order

See merge request gitlab-org/gitlab!23949

- Date time range utils to support basic time range operations
- Monitoring utils to support time ranges in the url of dashboards

This is to prevent specs from failing due to changes in docs