test-utilities: version test

[raboof]

Motivation for this change

Make adding version tests more likely by making it easier, as
discussed in #119636 (comment)

Long-term I hope 'upstreaming' the tests could replace the functionality
in nixpkgs-update as discussed in
nix-community/nixpkgs-update#260

Things done

• Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
• Built on platform(s)
  • NixOS
  • macOS
  • other Linux distributions
• Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
• Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
• Tested execution of all binary files (usually in ./result/bin/)
• Determined the impact on package closure size (by running nix path-info -S before and after)
• Ensured that relevant documentation is up to date
• Fits CONTRIBUTING.md.

[roberth]

Suggested change

	}: runCommand "test-version" { buildInputs = [ package ]; meta.timeout = 60; } ''
	}: runCommand "test-version" { nativeBuildInputs = [ package ]; meta.timeout = 60; } ''

buildInputs is for components (linking etc) and not for running. With cross compilation and in the future with strictDeps, these components will not be added to PATH.

@Ericson2314 do you think it's feasible to send this to a remote builder in case of cross compilation? Do we an attribute à la pkgs.buildPackages for this purpose? (I've tried hostP{ackages,*}, remoteP*, testP*)

You'd need a remote builder, but that's better than not being able to run this at all.

[davidak]

Haven't seen this until now. This is awesome. Thank you very much! ✨