Rust: limit number of diagnostics to 100 per trap file

[aibaars]

This pull request limits the number of error/warning/info diagnostics we store in the CodeQL database to 100 per file. This should avoid SARIF from growing too large.

[Copilot]

Pull Request Overview

This PR adds a hard cap of 100 diagnostics per trap file to prevent excessive emissions.

• Introduced an emit_diagnostic_limit field on Translator and initialized it to 100.
• Added EMIT_DIAGNOSTIC_LIMIT_PER_FILE constant and applied a check/decrement in the diagnostic emission path.
• Kept existing behavior for Debug-level diagnostics (they are not counted against the limit).

Comments suppressed due to low confidence (2)

rust/extractor/src/translate/base.rs:126

• Add a doc comment for the emit_diagnostic_limit field (and for EMIT_DIAGNOSTIC_LIMIT_PER_FILE) to explain its purpose and units, so future maintainers understand its role.

    emit_diagnostic_limit: usize,

rust/extractor/src/translate/base.rs:251

• No tests were added to verify that diagnostics stop after the limit is reached; consider adding a unit or integration test that emits over 100 diagnostics and asserts that subsequent ones are suppressed.

        if severity > DiagnosticSeverity::Debug && self.emit_diagnostic_limit > 0 {

[Copilot]

[nitpick] Consider making the diagnostic limit configurable (e.g., via a constructor argument or config file) instead of a fixed constant, which would improve flexibility and allow per-project adjustments.