Add compatibility-aware navigation scoring

[DavidBakerEffendi]

Description

Add compatibility-aware destination scoring without changing the audited declaration and definition ground truth. This separates the destination users can reach from strict adherence to the case's canonical LSP operation, allowing implementations that expose the same destination through the other navigation API to receive recall credit while preserving protocol-precision reporting.

Key Changes:

• Add explicit compatibleOperations benchmark metadata and execute compatible navigation routes separately in the Bifrost and LSP runners.
• Report per-case requiredDestinationStatus and aggregate required-destination totals while retaining the existing strict canonical status and totals.
• Annotate audited Go, JavaScript/TypeScript, and PHP cases and update the methodology, language pages, and result tables from fresh analyzer reports.
• Validate compatible operations in the runtime model and checked JSON schema, with regression coverage for fallback isolation, unavailable routes, partial results, extra destinations, and report serialization.

Touch Points:

• src/runners/
• src/lib.rs
• src/main.rs
• schema/benchmark-case.schema.json
• benchmarks/cases/
• benchmarks/README.md
• docs/src/content/docs/

Validation

• cargo test --lib --bins
• cargo run -- validate benchmarks/cases
• npm --prefix docs run check
• Fresh Bifrost, gopls, TypeScript language server, and Intelephense reports with zero runner errors