ci: Ensure that cargo-nextest is at least at version 0.9.72 to prevent breakage with Rust 1.83

[osiewicz]

Check for existing issues

• Completed

Describe the bug / provide steps to reproduce it

While dry-running new Rust release (in anticipation of Rust 1.85 release) I've noticed that cargo nextest run --workspace fails on derive_refineable failing to find libstd.dylib. This can be tracked down to 1.83 - in particular this change. The culprit lies elsewhere - I've had an old version of cargo nextest in my environment; it looks like starting with Rust 1.83, we'll have to use cargo-nextest >= 0.9.72 in our CI (as it includes the fix in nextest-rs/nextest#267).
This issue is really just there for me to remember about when upgrading the Rust version in a month or so.

Zed Version and System Specs

Zed: v0.168.2 (Zed)
OS: macOS 15.1.0
Memory: 64 GiB
Architecture: aarch64

If applicable, add screenshots or screencasts of the incorrect state / behavior

No response

If applicable, attach your Zed.log file to this issue.

Zed.log