This change moves buildGoPackage from pkgs/development/go-modules to
pkgs/development/go-packages, so we can have buildGoModule at
pkgs/development/go-modules.

(cherry picked from commit a0d835e)

The function buildGoModule builds Go programs managed with Go modules. It builds
a Go module through a two phase build:

- An intermediate fetcher derivation. This derivation will be used to
  fetch all of the dependencies of the Go module.
- A final derivation will use the output of the intermediate derivation
  to build the binaries and produce the final output.

(cherry picked from commit 28435e4)

In order to build the package databases that we will use when compiling
a Haskell package, we iterate over the relevant dependencies, and if
they contain a package db, we copy its contents over.

So far so good, except when one of those dependencies is GHC. This
doesn't happen ordinarily, but it will happen when we construct the
package database for compiling `Setup.hs`.  This is compiled for the
build architecture, so we get the build deps, including both the native
and the cross GHC (if there is one).

In this case, we end up copying the packages from the GHC's package
database. This is at best unnecessary, since we will get those packages
from the GHC when we compile with it.

At worst, however, this is semantically questionable. We can end up
having multiple copies of e.g. Cabal with the same version, but
(potentially) different contents. At the moment, GHC will expose one of
these at semi-random depending on which one it looks at "first".
However, there is a MR open [in
GHC](https://gitlab.haskell.org/ghc/ghc/merge_requests/545) which as a
side effect will instead expose both, leading to ambiguous module
warnings (which is not unreasonable, since it *is* ambiguous).

So what can we do about it? The simplest solution is just to not copy
the package databases from GHC. GHC is special in this regard, so I
think it's okay to treat it specially.

This PR should have no effect on anything now, but will prevent any
breakage when/if the GHC patch lands.

Closes NixOS/nixpkgs#57706.

(cherry picked from commit 387c513)

(cherry picked from commit b1454f5)

From https://csvkit.readthedocs.io/en/1.0.3/index.html:
> csvkit is a suite of *command-line tools* for [...]

(cherry picked from commit 5e39aa2)

fallout of NixOS/nixpkgs#54182
fixes NixOS/nixpkgs#57263

(cherry picked from commit ea7885f)

Backport of #57284
(cherry picked from commit 79e3dcb)

Otherwise, tests fail with
> Failed: [pytest] section in setup.cfg files is no longer supported, change to [tool:pytest] instead.

(cherry picked from commit 8f115c0)

(cherry picked from commit 832eb25)

(cherry picked from commit 379ff38)

buildGoModule: backport the new Go infrastructure to release 19.03