clippy is not installed to destination dir if 'tools' config variable not explicitly defined.

[ebeasant-arm]

Found whilst performing a extended tools release bootstrap build on aarch64:

Unless 'tools' is explicitly specified in config.toml with an extended build config, clippy is not installed, it is explicitly skipped as it does not appear in builder.config.tools (src/install.rs, Line: Line: 158, Line: 222)
Clippy is actually built for stage 2, but not installed by install.py.
Of the default extended tools built when extended-tools are enabled, only clippy seems to behave like this.

If this is intended behaviour, then a note in the config.toml indicating this would be helpful :-)

This occurs using the default channel (dev) in config.toml, constructed only using ./configure --enable-full-tools --prefix=$RUST_TOOLCHAIN_DIR --sysconfdir=$RUST_TOOLCHAIN_DIR on aarch64 native host.

[Mark-Simulacrum]

cc @oli-obk probably fallout from the subtree migration

[imogenkinsman]

I can investigate this if that's okay - would be a good way for me to familiarize myself with rust's build system.

[imogenkinsman]

@rustbot claim

[imogenkinsman]

I can't verify this issue on master until #72231 is resolved, as that's blocking extended tools builds.

[mati865]

@jademcgough you can use missing-tools or tools config.toml options.

[imogenkinsman]

@mati865 Thanks! missing-tools was perfect for unblocking me.

Traced it to regression caused by a182450. Should have a fix for this tomorrow.

[Alexendoo]

Triage: Hi, are you still working on this issue @immykins?

[Alexendoo]

@rustbot release-assignment

[Enselic]

Triage: Is this still a problem?