Fix user_sorts_issues_spec when vue_issuables_list ff is off

See merge request gitlab-org/gitlab!38423

[Feature flag] Rollout of `sidekiq_versioning`

Closes #232934

See merge request gitlab-org/gitlab!39562

Update distributed reads spec

See merge request gitlab-org/gitlab!39412

Add single request context to MR Analytics

See merge request gitlab-org/gitlab!39726

Expose ID in API Event Entity

Closes #238141

See merge request gitlab-org/gitlab!39669

Update dependency @gitlab/ui to v20.3.1

See merge request gitlab-org/gitlab!39722

Add isSingleRequest to docs

See merge request gitlab-org/gitlab!39729

Revert "Merge branch 'ajk-relative-positioning-improvements' into 'master'"

See merge request gitlab-org/gitlab!39787

[RUN AS-IF-FOSS] Revert "Merge branch 'ss/mv-swimlanes-comp-to-ee' into 'master'"

See merge request gitlab-org/gitlab!39790

Migrate checkout step summary buttons away from legacy buttons

Closes #219800

See merge request gitlab-org/gitlab!39561

Merge branch '238530-add-new-diff-note-icon-on-commit-page-is-currently-broken-on-canary' into 'master'

Fix broken add note icon styles on Commit#show page

See merge request gitlab-org/gitlab!39789

This reverts merge request !38724

Fix time zone config not respected in multi-threaded servers

Closes #233259

See merge request gitlab-org/gitlab!39778

Issues api - allow empty due_date arg

See merge request gitlab-org/gitlab!39770

Time.now => Time.current usage in /lib [RUN AS-IF-FOSS]

See merge request gitlab-org/gitlab!36908

GraphQL Iterations - add scopedPath and scopedUrl

See merge request gitlab-org/gitlab!39543

Previously in multi-threaded app servers, such as Puma, the Rails time
zone configuration setting was not being respected. Rails expects the
time zone to be set in `application.rb`, and the default value is set in
the `active_support.initialize_time_zone` Railtie. However, since we
load this setting from a config file, the time zone for GitLab is set
inside an initializer.

Setting `Time.zone` in the initializer worked fine with Unicorn, but it
stopped working with Puma. All responses would return timestamps in UTC,
irrespective of the system or Rails time zone. This happened because
`Time.zone` calls `Thread.current`. Since the time zone wasn't set for
the thread, Puma would default to `Time.zone_default`, which was UTC.

We now set the default and the Rails configuration settings to be
consistent.

Closes https://gitlab.com/gitlab-org/gitlab/-/issues/233259

This reverts merge request !37724

Update Snowplow Availability of Snowplow Mini on Staging and Production

See merge request gitlab-org/gitlab!39775

Whats New - drop content for 3 previous releases

See merge request gitlab-org/gitlab!38976

Set default for current_value in SAST config UI

See merge request gitlab-org/gitlab!39504

Split board_conent logic between ee and ce compoents

See merge request gitlab-org/gitlab!38724

Remove exact repetition in .gitignore

See merge request gitlab-org/gitlab!39776

Add model for CiliumNetworkPolicy

See merge request gitlab-org/gitlab!38848

https://gitlab.com/gitlab-org/gitlab/-/merge_requests/38003

Docs: How to remove a license

See merge request gitlab-org/gitlab!39773

Replace fa-pencil icon with GitLab SVG

Closes #225951

See merge request gitlab-org/gitlab!39648

- replace last fa-pencil instance

Add specs to detect reindexing UI issues

See merge request gitlab-org/gitlab!39578

These two new fields are meant to be used inside a project query in
order to return a path scoped to the project that looks like
/path/to/project/-/iterations/inherited/iteration_id