podman: fix cross compilation build

- See `Nixpkgs` issue 467994 for detailed build logs showing the
  failure.

- `Podman` will use its vendored version of `go-md2man` when the
  `GOMD2MAN` environment variable is unset.

- When cross compiling from `x86_64-linux` to `aarch64-linux`, this
  results in the tool being compiled with the `aarch64-linux` compiler
  using `x86_64-linux` options. The compiler arch is wrong, so the build
  fails.

- To circumvent this use `Nixpkgs` version of `go-md2man`.

- The current vendored version matches `Nixpkgs` version (v2.0.7):
  containers/podman@7e14a03

- The reason for the vendoring is detailed in this commit:
  containers/podman@dfec510

(cherry picked from commit 0dd94f0)

Author: magicquark

pkgs/by-name/po/podman/package.nix

@@ -5,14 +5,14 @@
   pkg-config,
   installShellFiles,
   buildGoModule,
+  buildPackages,
   gpgme,
   lvm2,
   btrfs-progs,
   libapparmor,
   libseccomp,
   libselinux,
   systemd,
-  go-md2man,
   nixosTests,
   python3,
   makeBinaryWrapper,
@@ -70,7 +70,6 @@ buildGoModule (finalAttrs: {
 
   nativeBuildInputs = [
     pkg-config
-    go-md2man
     installShellFiles
     makeBinaryWrapper
     python3
@@ -89,6 +88,7 @@ buildGoModule (finalAttrs: {
   env = {
     HELPER_BINARIES_DIR = "${placeholder "out"}/libexec/podman"; # used in buildPhase & installPhase
     PREFIX = "${placeholder "out"}";
+    GOMD2MAN = "${buildPackages.go-md2man}/bin/go-md2man";
   };
 
   buildPhase = ''