[post-mortem] improve yank flow for cargo-nextest

[sunshowers]

In #926, it took almost 20 minutes to fully yank the bad version. We need to improve our story here -- yanking a bad release should take under 5 minutes at most.

• Add test for v0.9.56 Always Fails Due to Missing Config File #926.
• Move commands from GH Actions to scripts/.
• Add a mukti-bin yank command.
• Build automated CI tooling to yank bad versions.
• Work with Taiki to create a signal to update taiki-e/install-action.
  • Addressed by install-action always using cargo-binstall, making it so that we have control over nextest's releases.

[thomasmost]

FWIW my GitHub actions flow is still broken, using taiki-e/install-action@nextest

[sunshowers]

Ah yes, didn't realize the install-action had picked it up already. Taiki needs to update it on his end: taiki-e/install-action#178

[sunshowers]

You can check in an empty .config/nextest.toml as a temporary workaround.

[thomasmost]

Thank you!