Reverse correlation ID propagation

See merge request gitlab-org/labkit!117

Allow to retrieve correlation ID from metadata

See merge request gitlab-org/labkit!119

style: updating linting rules

See merge request !118

Introduce Stackdriver Trace support

See merge request gitlab-org/labkit!116

With GitLab 14.0 the `@semantic-release/gitlab` version no longer works
as pointed out in
https://github.com/semantic-release/gitlab#breaking-changes-in-140 run
`npm update` and use `node` 14.0 (latest LTS version) so that we have
all node dependecies updated and working as expected.

ci: update semantic release packages

See merge request gitlab-org/labkit!120

Ensure correlation id header is always added to response

See merge request gitlab-org/labkit!121

Inline functions

See merge request gitlab-org/labkit!122

In order for us to propagate correlation IDs from Gitaly to Workhorse,
which generates its own correlation IDs, we need to enable the
propagation option. However, we don't want to allow just anyone to spoof
a correlation ID request. We add a trusted CIDR block list so that we
can restrict propagation to internal hosts.

Part of gitlab#324836

Support trusted IP list for propagating correlation ID

See merge request !123

Use the variable `$CI_MERGE_REQUEST_DIFF_BASE_SHA` instead of
`$CI_MERGE_REQUEST_TARGET_BRANCH_SHA` as it is only available in pipelines for
merged results and not available for draft MRs either.

Closes gitlab-org/labkit#34

fix: use MR diff SHA in commitlint job

Closes #34

See merge request gitlab-org/labkit!124

The default behaviour of labkit logging is to use the local timezone
for log messages. However, gitlab-shell wants to use UTC in all cases.

Add a WithTimezone LoggerOption to allow configuring this behaviour.

Add log.WithTimezone()

See merge request gitlab-org/labkit!127