testers.testBuildFailure': init

[ConnorBaker]

In writing tests for #383214, I was irritated by the amount of boilerplate to do simple things like check for the presence of strings in the builder's log or assert that the builder's exit code was some value.

This PR introduces testBuildFailure', a wrapper around (and maybe eventually a replacement for) testBuildFailure.

An example of the rewrites testBuildFailure' enables, take a look at the tests in #383516 compared to the tests in #383214.

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
  • sandbox = relaxed
  • sandbox = true
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• 25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
• Fits CONTRIBUTING.md.

---

Add a 👍 reaction to pull requests you find important.

[philiptaron]

I like this a lot. The suggestion to make use of lib.customization.extendMkDerivation is not blocking.