treewide: remove "with lib;" from meta

[zeuner]

This PR changes a lot of packages treewide to remove the with lib; pattern from meta.

This removes one with scope. Furthermore, in many PRs that add a package there is a review that asks for adding or removing with lib; from the meta expression (I encountered both requests). It would be more efficient if there was one way to write meta on which we can all agree. There is https://nix.dev/guides/best-practices.html#with-scopes stating that with scopes should not be used for large scopes. meta could be considered a small scope, though.

There is also the opposite done in #373548. Of course, it only makes sense to merge either this PR or the other one. I can live with either choice, but the codebase should reflect that choice (which is what this PR aims for), and it should be documented.

For now, I only consider .nix files that are already formatted with nixfmt.

Things done

• Verified all patches leave the value of the meta attr they touch unchanged.
• 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.

[wolfgangwalther]

This has over 44k lines changed. This is impossible to review like this. How did you create this? Is there code that you can share to reproduce this, so that this can be validated?

[wolfgangwalther]

• Verified all patches leave the value of the meta attr they touch unchanged.

Also code/commands to easily verify this claim would be appreciated!

[wolfgangwalther]

Superseded by #443046.