The anonymous function is bound to the loop variables which change
their content. This works with the current Ginkgo v1.12.1
where Describe calls the function immediately, but in Ginkgo v1.14.1
that changes and the function is stored and called much later.

To prepare for that, each function instance must be bound to copies of
the loop variables. Otherwise for example a test for
"operator" runs with the deployment for "direct-testing".

This is the result of `go get -u ./...` with some manual tweaks:
- gopkg.in/square/go-jose.v2@v2.2.2 and google.golang.org/grpc@v1.27.0
  because that is what Kubernetes uses and newer versions
  changed the API such that Kubernetes code doesn't compile
- github.com/operator-framework/operator-sdk/version was made
  an internal package, so we can't use it anymore
- github.com/operator-framework/operator-sdk/pkg/restmapper was
  removed - we don't seem to need it anymore

When we get an unexpected status code like 500, the body contains an
explanation of what went wrong.

To see log output, we must initialize the arguments and run the test
with -v=5.

The new release adds support for process_start_time, which we don't
need and don't want because we already get it through the Prometheus
Golang collector.

Worse, if we keep it enabled in the metrics manager, then metrics
collection fails because the two definitions are slightly different,
which Prometheus treats as an error.