lib/customisation: add NoMkOverridable variants of callPackage

[Artturin]

in some places we want to use callPackage but don't want to inject the makeOverridable attrs so far import with manual inherits has been used

Description of changes

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
• 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/)
• 23.05 Release Notes (or backporting 22.11 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.

[roberth]

IIUC, the purposes of callPackage are all of:

• Using splicedPackages (as opposed to unspliced)
• Adding overriding
  • specifically override
  • also mkDerivation overriding attrs, but only out of necessity, for multi layer overriding to be somewhat coherent.
• The same thing that lazyFunction does (lib.lazyFunction: init #194514)

So by removing overriding, it seems that you could simplify all this by leaving callPackage untouched and instead implementing this variation with lazyFunction and splicedPackages instead. callPackage is already rather complicated, so that would be much nicer.