Point users to crate authors on cargo-install failures

[epage]

Seeing issues like #11484 made me wonder if there is something we can do to help users.

For example, what if git and registry installs had a note at the end that pointed people to the repository link in the manifest? The main risk is sending people to the wrong place for cargo bugs but the likelihood of that seems low enough and it shouldn't confuse the person triaging it as they are likely the crate author and more likely to tell apart failures in their crate vs cargo failures.

[weihanglo]

Which one should we suggest users going to, the repository of the final artifact or the failing crate? Looks at this issue starship/starship#4310. The root cause varies case by case. The fix for it is probably telling a dependency to release a new SemVer-compatible point release, though it could also be the dependant crate forgot to turn a feature on.

This is a relatively safe error message enhancement. Once we decide, I guess we can just call for help and move on.