fix: don't spam repeated error messages when `cargo check` fails

Conceptually, using a *message* here is wrong, because this is a
"status", rather than "point in time" thing. But statuses are an LSP
extension, while messages are stable. As a compromise, send message only
for more critical `metadata` failures, and only once per state change.

0 files changed, 0 insertions, 0 deletions