fix(my-lsp): handle CheckError::ResourceViolation (restore workspace build)

PR #127 added the `CheckError::ResourceViolation` variant but missed the
exhaustive `match` in `my-lsp::extract_error_location`, so `my-lsp` failed to
compile in a full `cargo --workspace` build (error[E0004], non-exhaustive
patterns). `cargo test -p my-lang`/`-p my-qtt` didn't catch it because they
never build my-lsp.

This is the true root cause of the `llvm-cov` "no profraw files" failure: the
coverage job runs `cargo llvm-cov --no-report --workspace --exclude my-llvm`,
which couldn't build my-lsp, so no tests ran and no profraw data was produced —
surfacing only as the downstream report-step error. Adding the missing arm
restores the workspace build; `cargo test --workspace --exclude my-llvm` is
green again.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BwV2DWsjkBiNP3oscimMLV

Author: claude

.clusterfuzzlite/Containerfile

@@ -120,6 +120,7 @@ fn extract_error_location(error: &CheckError) -> (usize, usize) {
         CheckError::NonBoolCondition { line, column, .. } => (*line, *column),
         CheckError::ExpressionTooDeep { line, column, .. } => (*line, *column),
         CheckError::Other { line, column, .. } => (*line, *column),
+        CheckError::ResourceViolation { line, column, .. } => (*line, *column),
     }
 }