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

Subtle ellipsis for loading state for large blobs

See merge request gitlab-org/gitlab!66652

Add a badge for project invite members

See merge request gitlab-org/gitlab!66611

MR-widget: Make vulnerability-dismissal error more descriptive

See merge request gitlab-org/gitlab!66722

Debian CRUD group distribution endpoints

See merge request gitlab-org/gitlab!66188

Remove ci_build_trace_section related application code

See merge request gitlab-org/gitlab!66574

Add group runners page [RUN AS-IF-FOSS]

See merge request gitlab-org/gitlab!66376

Create/Read/Update/Delete group distributions

Changelog: added

Disable creating user mentions during import

See merge request gitlab-org/gitlab!66792

Merge branch '333944-add-snowplow-tracking-to-audit-events-date-range-segmented-control' into 'master'

Add Snowplow tracking to audit events date range segmented control

See merge request gitlab-org/gitlab!66443

This adds the tracking data attributes to the audit events date range
buttons. This will be picked up by snowplow and used to determine if the
buttons are actually used

Remove the application code that populates the ci_build_trace_sections
and ci_build_trace_section_names. This data is not read by the
application currently and we can save on space/maintaince and solve
problems with background migration for self-managed users by dropping
the table is subsequent MRs.
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/66674

This table was originally created to collect metrics on jobs but was
never used and an expiration policy of was never enforced.
https://gitlab.com/gitlab-org/gitlab-runner/-/issues/2505

There is the possibility that we will need to build out features that
need this data in the future, based on the future vision, but at this
time it is not being used, and we can re-add it while re-considering
the architecture at that time (likely in 2022).
https://gitlab.com/gitlab-org/gitlab/-/issues/32565

docs: Use gotestsum in Unit test reports Go example

See merge request gitlab-org/gitlab!66787

Minor improvements of group search

See merge request gitlab-org/gitlab!66736

Clean up Ruby 3 related deprecation silences

See merge request gitlab-org/gitlab!66820