Merge branch 'security-maven-dependency-proxy-xss' into 'master'

See merge request gitlab-org/security/gitlab!4227

Changelog: security

Contributes to https://gitlab.com/gitlab-org/gitlab/-/issues/466031

**Problem**

For Cells and Geo needs we want to route Git push over SSH requests to
the correct instance.

**Solution**

Introduce an HTTP Workhorse endpoint that accepts git push requests
coming from GitLab-Shell and responds with git receive pack data.

Changelog: added
EE: true

Changelog: fixed

Workhorse tests don't currently support running with Gitaly's
transactions enabled. This commit adds support for doing so.

Rails can be configured to run tests with transactions using the
`GITALY_TRANSACTIONS_ENABLED=true` environment variable. If the
variable is set, Workhorse now also runs with Gitaly with
transactions.

Workhorse sets up the Gitaly configuration by copying the
configuration file set up via `scripts/setup-test-env` and
overriding the connection details. This part is adapdted to pick
the Gitaly configuration file with or without transactions
depending on the environment variable.

We also adjust gitaly_setup.rb to respect the configuration file
provided by Workhorse instead of overriding it with the transaction
enabled Gitaly configuration Rails tests use.

This commit fixes all the tests to shut down the HTTP requests and
test servers so that the TestMain() in each package can properly check
for Goroutine leaks.

This is a follow-up to
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/156420. We had a
long-standing Goroutine leak, but for some reason it only became a
a problem after the upgrade to Go 1.22.3 from 1.21.9. This adds some
Goroutine leak checks in some of the artifact upload tests.

Relates to
https://gitlab.com/gitlab-com/gl-infra/capacity-planning-trackers/gitlab-com/-/issues/1796

Ignore `Function 'generateMetadataFromZip' is too long` errors for
now.

We've seen in production the number of Goroutines in Workhorse exceed
4000. The pprof output suggests that many of these came from the
logrus Goroutines lingering.

When Workhorse forks `gitlab-zip-cat` and `gitlab-zip-metadata` it
attempts to log all stderr via a logrus Writer. logrus launches a
Goroutine to listen from a pipe. We should ensure this Writer is
closed so that the Goroutines shut down as soon as possible.

Changelog: fixed

Contributes to https://gitlab.com/gitlab-org/gitlab/-/issues/456116

**Problem**

For Cells and Geo needs we want to route Git over SSH requests to the
correct instance.

**Solution**

Introduce an HTTP Workhorse endpoint that accepts requests coming
from GitLab-Shell and responds with git upload pack data.

Changelog: added
EE: true

Contributes to
https://gitlab.com/gitlab-org/quality/engineering-productivity/master-broken-incidents/-/issues/6747

**Problem**

The previous certificate that was used in tests got expired. As a result
tests started failing with "tls: failed to verify certificate: x509:
certificate has expired or is not yet valid: current time
2024-06-07T06:16:03Z is after 2024-06-07T04:31:24Z"

**Solution**

Reissue a certificate with an expiration date "Aug 24 09:26:29 2032 GMT"

Changelog: fixed