Use cached cargo-install

[TriplEight]

I assumed @tomaka didn't like cargo-nextest so not suggesting it here.
Here you go, 1sec instead of 2 min

[github-actions]

twiggy diff report

Difference in .wasm size before and after this pull request.

---

 Delta Bytes │ Item
─────────────┼──────────────────
          +0 ┊ Σ [0 Total Rows]

[tomaka]

Thanks

[tomaka]

I assumed @tomaka didn't like cargo-nextest so not suggesting it here.

That's not true. I'm cautious against being overly reliant on tools like this, not avoiding using them. For example parsing the programmatic output of cargo nextest wouldn't be a good idea.

[TriplEight]

just nagging you there :)

For example parsing

yes, indeed, but do you parse it?

[tomaka]

What I mean is that if cargo nextest happened to be abandoned over night, we should be able to switch back to cargo test easily. If we were analyzing the output of cargo nextest and performing important actions depending on the result, we would lose the possibility to easily switch back to cargo test.

[TriplEight]

yeah, this is a normal concern, but considering how rarely we end up parsing i.e. test outputs I think it's worth discussing this probability when we're about to parse some outputs.