Use best practice from k8s for code coverage and linters

[sebastienvas]

According to @fejta, Kubernetes is using a fork of gazelle and have code coverage and linters done differently. @ixdy might be able to help us.

[ixdy]

we're currently using a completely separate tool (https://github.com/mikedanese/gazel) which shares no code with gazelle but accomplishes much of the same things, along with some kubernetes-specific functionality, notably https://github.com/mikedanese/gazel/blob/master/gazel/generator.go and https://github.com/mikedanese/gazel/blob/master/gazel/sourcerer.go.

we're planning to switch to gazelle and use gazel (or a successor) only for the non-Go functionality. it sounds like that might be what you're interested in.

[ixdy]

but an example of how we do linting is in https://github.com/kubernetes/test-infra/blob/952eca86f9e255c9b87240a5f2b8f27bfa57ff3f/verify/BUILD#L29-L36

[BenTheElder]

Note that prow has had a plugin for /lint which covers golint at least, I think we have more work to do on these fronts though.