darwin.stdenv: format with nixfmt-rfc-style

[reckenrode]

Description of changes

I’m going to be doing a lot of work on the Darwin stdenv. Rather than risk merge conflicts, I’d like to get it reformatted before I start working. I confirmed with nix-instantiate that the resulting hash for the stdenv is the same, so it should not cause rebuilds. This is targeting staging-next because staging-next will merge in a few days. Currently, staging and staging-next have the same base commit.

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/)
• 24.11 Release Notes (or backporting 23.11 and 24.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.

[emilazy]

Commit message typo needs fixing. (And darwin.stdenv: update .git-blame-ignore-revs feels backwards to me, though apparently other people are using that style…)

LGTM otherwise, given that ofborg says 0 rebuilds.

[reckenrode]

I fixed the typo in the commit message. Once checks are green, I’ll merge.