Mention cargo wizard in build performance guide

[Kobzol]

I figured that since we already mention other third-party Cargo subcommands, we could also mention my cargo-wizard tool, as it's (IMO) highly relevant here.

r? @epage

[weihanglo]

Nice. I don't have any objection. I would let Ed to decide to merge or not. (Or other having opinions)

View changes since this review

[epage]

I'm hesitant about this and I'm not sure why.

Possibilities:

• The tools we link out to are generally specific in scope while this is more open ended in purposes making it hard to track what we are soft-endorsing
• The strong language, making it sound like cargo wizard replaces this documentation when it doesn't fully
• We are trying to capture specific nuance and may even want to limit what we recommend and being unsure how well that applies to cargo wizard

[Kobzol]

I view the existing tool recommendations as "if you don't want to do this manually, this tool can do it for you", and I'd like to say something similar about cargo-wizard. So maybe something like "cargo-wizard can automatically apply some of the configuration options mentioned below, so that you do not have to do it manually for each project"? Or something like that.

[rustbot]

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