feat(oxlint): Add Bitbucket Code Insights output formatter

[ild0tt0re]

Summary

Adds a new Bitbucket output formatter for oxlint that emits diagnostics as Bitbucket Code Insights annotations (bulk annotations JSON) so CI can upload reports to Bitbucket.

Why

Enable Bitbucket Code Insights integration by producing the exact annotation payload expected by Bitbucket reports endpoints. This lets CI workflows surface linter issues directly in Bitbucket's UI.

What changed

• Added: bitbucket.rs — implements BitbucketOutputFormatter, BitbucketReporter, and serialization types.
• Mapping: Maps Severity → Bitbucket annotation_type/severity (Error→BUG/HIGH, Warning→CODE_SMELL/MEDIUM, Advice→CODE_SMELL/LOW).
• Repo paths: Detects git repo root and prepends repo-relative prefix (handles Windows path normalization).
• Deterministic IDs: Generates stable external_id per diagnostic using a deterministic hash.
• Tests: Unit tests covering serialization, path prefixing, severity mappings, and external_id determinism.

Compatibility / Migration

Non-breaking — new formatter only; existing formatters unaffected. To use, select the bitbucket formatter when running oxlint in CI and POST the resulting JSON to Bitbucket Code Insights annotations endpoint.

[camc314]

@ild0tt0re can you include an example of what this looks like in bitbucket?

[nrayburn-tech]

There’s an example screenshot about halfway down this page under the “Hiding annotations from the diff view” section.
https://confluence.atlassian.com/bitbucketserver100/code-insights-1680278535.html

It’s the part in the code diff showing as “low” and as a “WCAG” issue.

It’s a similar UI concept to the GitHub feature.