Suggest another toolchain when removing a component/target unavailable to the current toolchain

[FlareFlo]

Problem you are trying to solve

1. rustup update fails (unrelated to issue)
   
2. rustup target remove wasm32-wasi fails
   
3. rustup +target remove wasm32-wasi succeeds, as the default toolchain was nightly as specified in .rustup/settings.toml

Solution you'd like

Rustup could search and suggest targets on other versions when the default does not have the target

Notes

No response

[FlareFlo]

This issue is not a dupe of #4099
Any other target has the same issue, i just happened to use wasm32-wasi as mentioned in the problem description

[rami3l]

This issue is not a dupe of #4099 Any other target has the same issue, i just happened to use wasm32-wasi as mentioned in the problem description

@FlareFlo My apologies.

IMO your original issue in particular does fall into the larger category of our properly informing the users of a target name change. However, WRT potential misoperations such as trying to remove a component installed only in another toolchain, I do think that will be a possible aspect to be improved.

I've adjusted the title according to what I think you was trying to address. Please let me know if you think that is inaccurate.