Support -Zno-link

Describe the problem you are trying to solve
Compilation pipelining can currently compile dependent crates as soon as the crate metadata is written in most cases. This improves cpu utilization for from-scratch builds. It is however not possible to apply pipelining on crates that need to be linked like executables and dylibs as all object files need to be available to link something.

Describe the solution you'd like
Using the -Zno-link option of rustc it is possible to separate the compilation and linking step. This makes it possible to pipeline the compilation and only wait for all crates to be fully compiled once we want to link the final executable. This option was introduced in https://github.com/rust-lang/rust/pull/68487 and fixed in https://github.com/rust-lang/rust/pull/80187 (now with a test to prevent regressions).

Notes
cc https://github.com/rust-lang/rust/issues/64191

To implement this rustc will first need to be invoked with -Zno-link as argument. This will produce all object files and a .rlink file. Once all dependencies are compiled you need to invoke rustc a second time with -Zlink-only as argument and the .rlink file instead of the source file.

Start by reading the compilation-pipelining context and the referenced rustc pull requests #68487 and #80187, along with issue #64191. Trace where Cargo invokes rustc for dependent crates and determine how to perform the two invocations: -Zno-link during compilation, followed by -Zlink-only with the .rlink file before final linking; done means linked crates can be pipelined without regressions.