We recentlly added the timelogs.summary column, but don't currently
have any mechanmic to populate it. This MR introduces a way to
populate via the API.

Changelog: added

Merge branch '336693-Migrate-prevent-forking-checkbox-to-gitlab_ui_checkbox_component' into 'master'

Migrate prevent forking checkbox to gitlab_ui_checkbox_component

See merge request gitlab-org/gitlab!66701

Resolve "Start and due dates are incorrectly set on epic creation"

See merge request gitlab-org/gitlab!66809

Remove deprecated runner set up instruction

See merge request gitlab-org/gitlab!66252

Remove Trial Suffix from Trial Plan Titles on Billing Page

See merge request gitlab-org/gitlab!66578

Date pickers emit Javascript Date instances and
these get converted to datetime strings with timezone info.

Ex. a user in UTC+9 timezone picks some date (say July 1).
The underlying Date object gets converted to a string
that uses UTC+0 as the default timezone and the date may
change becuase of this conversion:

'2021-07-01 UTC+9 Korean Standard Time'
=> '2021-06-30T??:??:??Z'

Changelog: fixed
EE: true

Tag workers that need their own queue

See merge request gitlab-org/gitlab!66553

Guidelines about using pgbouncer with multi-node Geo sites

See merge request gitlab-org/gitlab!66161

Add security scanners on Vulnerability-Check UI

See merge request gitlab-org/gitlab!66117

Add log count of active jobs

See merge request gitlab-org/gitlab!64623

Add support for propagation correlation IDs from trusted CIDRs

See merge request gitlab-org/gitlab!66715

Revise sentence for clarity about settings

See merge request gitlab-org/gitlab!66857

Remove flag guarding batched computation of changes size

See merge request gitlab-org/gitlab!66527

Test Auxiliary viewers with refactor_blob_viewer FF disabled

See merge request gitlab-org/gitlab!66816

Add remote tunnel variable for e2e tests

See merge request gitlab-org/gitlab!66656

E2E: large github import spec logging improvements

See merge request gitlab-org/gitlab!66810

Add comment explaining permission table sorting

See merge request gitlab-org/gitlab!66856

Removed old logo from image

See merge request gitlab-org/gitlab!66860

Update dependency @sourcegraph/code-host-integration to v0.0.59

See merge request gitlab-org/gitlab!66406

Docs: Update broken url in supported secrets section in the Secret Detection page

See merge request gitlab-org/gitlab!66869

Ensure even select values in UNION query [RUN AS-IF-FOSS]

See merge request gitlab-org/gitlab!66337

Switch from multi-line to single-line comments to avoid linting errors

See merge request gitlab-org/gitlab!66804

Collect all troubleshooting information

See merge request gitlab-org/gitlab!66827

TW OKR: Review UI text Packagist integration

See merge request gitlab-org/gitlab!66769

Quarantine a flaky spec

See merge request gitlab-org/gitlab!66855

When Gitaly makes internal API calls back to Workhorse in Git hooks,
Workhorse previously would generate new correlation IDs, making it hard
to trace the entire call flow.

In https://gitlab.com/gitlab-org/labkit/-/merge_requests/123, we added
the ability to propagate correlation IDs from trusted CIDR blocks.

To use this feature, we add two configuraton parameters:

* `trusted_cidrs_for_x_forwarded_for`
* `trusted_cidrs_for_propagation`

If propagation of correlation ID is enabled,
`trusted_cidrs_for_x_forwarded_for` tells LabKit what remote IPs can be
trusted to use the `X-Forwarded-For` HTTP header to resolve the actual
client IP. Note that this parameter is not yet used in Workhorse's
remote IP resolution, but it should be.

`trusted_cidrs_for_propagation` allows Workhorse to restrict propagation
to certain IP ranges. We will want to add the Gitaly servers to this
list.

Relates to https://gitlab.com/gitlab-org/gitlab/-/issues/324836

Changelog: added

Quickaction for changing an Issuable severity

See merge request gitlab-org/gitlab!66422