"Compose implementations of the same phase"

Issue description

Setup hooks (cmake, meson, pypa-build, etc) defining generic implementations for the common phases (configurePhase, buildPhase, installPhase, etc) weren't designed to be composed: cmake's setup-hook only injects its implementation of the configurePhase if the "slot" hasn't been occupied yet by someone else (e.g. meson). Moreover, since pre- and post-hooks are usually executed by the phase implementations (rather than by the caller), one couldn't "compose" different implementations of the same phase even manually without running the same hooks twice.

The particular issue with runHooks could be addressed by somehow moving the runHooks to generic/setup.sh, but more importantly we need a discussion on how to better accommodate these situations, and on how far to go in doing so (the "composition" of conflicting phases will likely always be manual)

Use-cases

dust3r

For instance, it's currently hard to reuse the functionality of cmakeBuildPhase and pypaBuildPhase in the same derivation. Here's a mildly cursed example of a package generating a setup.py using cmake where the phases have been composed "manually": https://github.com/SomeoneSerge/dust3r.nix/blob/4fd7d61310f2289ba9843c9854aaaf59837eafbd/nix/magnum-bindings/package.nix#L41-L56.

conda (libmambapy)

Here's a fresh example of a PR handling the non-trivial interaction of cmake and pypa-build: https://github.com/NixOS/nixpkgs/pull/296461/files#diff-dffa404ae86470475e60f1461b64526cb09a4bc5409a2e3d225fb262cbd81505R30-R33. This demonstrates that the tools nixpkgs offers are lacking for this kind of use-cases.

opencv

Nixpkgs' opencv expression is notorious:

cuda-samples

Here's a monorepo-like project with a top-level Makefile and some of the subprojects using CMake:

Prior art

TBD