This is to improve RAM usage when parsing references utilizing the
existing `cache` struct.

Reduces memory usage when parsing LSIF file of gitlab-workhorse
from 7MB to 4MB.

Add References struct

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

Add support for AWS S3 Server Side Encryption (SSE-KMS)

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

Extract references parsing logic to a separate file and struct.
Also modified `Item` struct to have `Line` as `int32` so it'll
be fixed size.

This is in preparation for another MR wherein references will be
stored in file instead of memory.

Prior to this change, uploads to AWS S3 were only encrypted on the
server if a default encryption were specified on the bucket.

With this change, admins can now configure the encryption and the AWS
Key Management Service (KMS) key ID in GitLab Rails, and the
configuration will be used in uploads. Bucket policies to enforce
encryption can now be used since Workhorse sends the required headers
(`x-amz-server-side-encryption` and
`x-amz-server-side-encryption-aws-kms-key-id`). The bucket policy cannot
be enforced with default encryption, since that is applied after the
check.

This requires the changes in
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/38240 to work.

Part of https://gitlab.com/gitlab-org/gitlab/-/issues/22200

Add changelog for MR 529

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

Added configuration option PropagateCorrelationID

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

added configuration option PropagateCorrelationID and corresponding flag argument propagateCorrelationID to enable correlation.InboundHandlerOption: WithPropagation() for correlation.InjectCorrelationID

Improve test report for performance_test.go

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

Drop Go v1.12 support

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

We officially use Go v1.13+ for everything
(https://docs.gitlab.com/ee/install/requirements.html#go-versions), and
dropping Go v1.12 allows us to use new methods such as
`http.NewRequestWithContext`.

Document changelog as part of process

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

Generating a changelog entry is now required when a merge request
warrants a CHANGELOG entry.

[ci skip]

Read and parse LSIF references

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

In order to be able to "Find references" of a given range or
definition, we need to be able to read `references` items from
the LSIF file.

This will then be written to the JSON file for each range via
`references` property.

The property will look something like:

```
"references": [
  {
    "path": "main.go#L7"
  }
]
```

Each reference will be an object with `path` property. The `path`
property will point to the exact line where it is being used.

This is currently behind a feature flag (`code_navigation_references`)
which will set `ProcessLsifReferences` header to `true` when
enabled. If `false`, the `references` won't be read and generated.

Refactor to prepare for parsing references

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

Eagerly delete private tempfiles

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

Preparation for supporting other type of item (e.g. references).

This MR includes the following changes:
- Rename `RawDefRef` to `RawItem`.
- Rename `DefRef` to `Item`.

Remove deprecated option

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

Add missing bounds checks in LSIF parser

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

Make upload filter code (EXIF, LSIF) more uniform

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

Log errors if lsif parser failed to close

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

[ci skip]

Use latest Golang in order to build code navigation

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

Cache hovers offsets in a file instead of a hash

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

Storing them in a hash consumes a lot of RAM
Introducing a file helps to reduce RAM consumption significantly

Cache ranges value in a file instead of a hash

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

Storing them in a hash consumes a lot of RAM
Introducing a file helps to reduce RAM consumption significantly

Use simplified setup for code intelligence

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