handle other PrepareErrors

[Skgland]

As of rust-lang/rustwide#103 rustwide 0.20 can now also return other PrepareErros than those already handled.
This sorts those into either prepare-fail or broken depending on whether we can identify a known underlying reason and whether that reason is spurious or not.
Spurious and unknown failures are categorized as prepare-fail and known non-spurious errors are classified as broken.

Note rustwide PR rust-lang/rustwide#98 is in progress and aims to reduce the cases that will be falsely classified as prepare-fail instead of broken.

rust-lang/rustwide#98 has been merged and the rustwide dependency has been bumped to a version including it.

[Skgland]

ping: This is waiting on review.

[Skgland]

ping, this is still waiting on review

@Mark-Simulacrum and @emilyalbini you two have reviewed PRs here in the past.

Summary

This now handles not explicitly handled PrepareError.
Tries to find the failure reason and then sorts spurious or unknown failure reason into
PrepareFail so that it lands on the retry-regressed-list.txt.
Known non-spurious failures are classified as BrokenCrate indicating a problem with the crate/repository.

Edit: Currently these get misclassified as error

Note: since this PR has been last updated rustwide has had more releases, maybe the rustwide dependency should be bumped further?

[Mark-Simulacrum]

Happy to bump rustwide further and then merge this, it seems fine to me.

[Skgland]

Happy to bump rustwide further and then merge this, it seems fine to me.

• ran cargo update in d490b35 to fix compilation on windows
• updated rustwide to latest version
• updated deps pulling in toml@0.8 to reduce duplicate deps
• updated test expectations as the error messages of the toml crate changed and apparently also the error code returned by rust for one of the minicrater crates