Don't compile on install without binaries

[yerke]

Fixes #8970

This PR is trying to revive the effort started in #9576.
We don't want to compile code if there is no viable binary when running cargo install my-name-here.

The PR in the current form is not great. Due to the new compile filter, we show warning: Target filter `bins` specified, but no targets matched. This is a no-op, even when the customer did not specify --bins.

I think one the way to address this issue would to update CompileMode::Build to CompileMode::Build { install: bool }, but I am not sure if that change would be welcome.

[rust-highfive]

r? @ehuss

(rust-highfive has picked a reviewer for you, use r? to override)

[yerke]

@ehuss Do you mind taking a look when you have time? Specifically, I want some guidance on this proposal:
I think one the way to address this issue would to update CompileMode::Build to CompileMode::Build { install: bool }, but I am not sure if that change would be welcome.

Of course, I would love to hear from @epage and @weihanglo as well :)

Thanks!

[ehuss]

I would prefer to not modify CompileMode as that breaks the abstraction with the lower-level code knowing about higher-level concepts like "install".

As mentioned in #9576 (comment), is it possible to adjust the checks to retain the error message?

[bors]

☔ The latest upstream changes (presumably #11410) made this pull request unmergeable. Please resolve the merge conflicts.

[yerke]

For now I don't have any good ideas on how to achieve this without modifying CompileMode::Build, so I will close this PR.