feat: make `which` mandatory
Splitting out `resolved`/`which` repository rules makes sense. It prevents any missing tools from raising an error in the toolchain resolution rather than later via the stub. This is _much_ more **user** friendly. Including the `resolved` target in the local repository was more **developer** friendly as it negated the need for two repositories. We want to be **user** friendly.
Loading