This updates Gitaly's latest Protocol Buffer definitions, which were
last updated in Feburary 2020, with the latest version of Gitaly. This
is needed to support a new flag (`IncludeLfsBlobs`) in the
`GetArchiveRequest` RPC.

Because we started tagging Gitaly versions `v13.x.x` instead of
`v1.x.x`, `go get` refuses to update the Gitaly module using the latest
tag or SHA (https://gitlab.com/gitlab-org/gitaly/-/issues/3177).  Go
tries to enforce semantic compatibility by requiring the use of module
paths (e.g. `m/v13`), and Gitaly doesn't adhere to this scheme.

To workaround this issue, we use the replace directive
(https://github.com/golang/go/wiki/Modules#when-should-i-use-the-replace-directive):

```
go mod edit -replace gitlab.com/gitlab-org/gitaly=gitlab.com/gitlab-org/gitaly@3f5e218def93024f3aafe590c22cd1b29f744105
```

Pass CORRELATION_ID env variable to resize image subprocesses

See merge request gitlab-org/gitlab-workhorse!612

Simplify s3 session management code

See merge request gitlab-org/gitlab-workhorse!616

Add image scaler duration Prometheus metric

See merge request gitlab-org/gitlab-workhorse!614

Bump labkit dependency to get mutex profiling

See merge request gitlab-org/gitlab-workhorse!599

[ci skip]

Add list of Workhorse "features" NO CHANGELOG

See merge request gitlab-org/gitlab-workhorse!613

Image scaler binary with pure golang lib

See merge request gitlab-org/gitlab-workhorse!603

Push uploader control flow into objectstore package

Closes #294

See merge request gitlab-org/gitlab-workhorse!608

[ci skip]

Fix correlation IDs not being propagated in preauth check

See merge request gitlab-org/gitlab-workhorse!607

Previously `info/refs`, `upload-pack`, `receive-pack`, and anything that
needed to make an authorization check with Rails would not forward along
the correlation ID injected in the request context. We solve this by
creating the HTTP request with the same context. This adds some
additional memory allocations for each outbound request.

Relates to https://gitlab.com/gitlab-org/gitlab-workhorse/-/issues/293

Update README.md to reflect only Go v1.13+ is supported NO CHANGELOG

Closes #268

See merge request gitlab-org/gitlab-workhorse!611

Increase LSIF scanner buffer

See merge request gitlab-org/gitlab-workhorse!609

Fix a typo in the message of image resizer NO CHANGELOG

See merge request gitlab-org/gitlab-workhorse!606

Fixes https://gitlab.com/gitlab-org/gitlab-workhorse/-/issues/268

Sometimes we receive bufio.Scanner: token too long is the parsed
string is too long

Let's increase the buffer size

Further simplify remote/local upload code

See merge request gitlab-org/gitlab-workhorse!602

Reflect the actual duration of bootstrapping GitLab

See merge request gitlab-org/gitlab-workhorse!605

Remove last cases of testify/assert NO CHANGELOG

See merge request gitlab-org/gitlab-workhorse!604

Signed-off-by: Takuya Noguchi <takninnovationresearch@gmail.com>

Signed-off-by: Takuya Noguchi <takninnovationresearch@gmail.com>

Only use testify/require in object storage tests NO CHANGELOG

See merge request gitlab-org/gitlab-workhorse!601

Replace some cases of testify/assert with require NO CHANGELOG

See merge request gitlab-org/gitlab-workhorse!600

Add project level route for generic packages upload

See merge request gitlab-org/gitlab-workhorse!596

Use strict filetype checks when calling `gm`

See merge request gitlab-org/gitlab-workhorse!564

By default, `gm` will ignore file extensions and determine the correct decoder/encoder based on the file's magic bytes. This means that a file pretending to be something else based on its extension might get processed.

According to http://www.graphicsmagick.org/security.html it is recommended to specify the reader based on the expected type instead by prefixing the input file with `jpg:` or `png:` respectively.

Also started to add unit tests for the image resizer. Coverage still a
bit spotty.

Add logging for local LSIF ZIP caching

See merge request gitlab-org/gitlab-workhorse!579