Use the LabKit logging infrastructure

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

Added param validation to help method TestAuthServer

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

Refactor error logging helpers

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

Fix Typos

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

Remove redirections from Terminal to Channel

Closes #214

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

feat: add option to set Sentry environment

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

Add a note about adding perl dependency

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

Release v8.7.0

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

Don't log http.ErrAbortHandler panics in sentry

Closes #219

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

Test against go1.12

Closes #217

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

We need to start testing against go1.12. I don't know if we can drop
support for go1.10 yet, so I've left that untouched for now.

Release v8.6.0

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

Add new endpoint to add support to proxy websocket requests to build's services

Closes #205 and gitlab-ee#5276

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

In this MR we add two endpoints for proxying requests
to services running inside the runner's builds.

One of the endpoints is for regular HTTP requests, while
the other is for websockets.

Release v8.5.1

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

Remove duplicate X-Request-Id response header

Closes gitlab-ce#60111

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

This fixes performance bar not working with AJAX requests.

Both LabKit and Rails were injecting duplicate X-Request-Id headers into
the response stream, which caused the frontend to be interpret the value
as a comma-separated value (e.g. LdEgVXsp1R4, LdEgVXsp1R4).

The new flow behaves as the following:

1. Workhorse injects X-Request-Id to the inbound HTTP request to Rails
2. Rails looks up this value in its RequestId middleware. Since the
value exists, Rails sets the X-Request-Id response header to this value.
3. Workhorse doesn't append another header in the response.

Distributed tracing should still work fine because Workhorse still
generates the correlation ID.

Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/60111

Release v8.5.0

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

Replace terminal terminology to channel

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

We're moving from using terminology related to terminal when
we refer to websockets connections. It's more generalistic
a concept like channel.

Release v8.4.0

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

Add code from the most recent security release to master

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