fix(ci): pin tree-sitter<0.26 to stop native segfault (#235)

[Wolfvin]

Mengapa

PR #262 memperbaiki YAML CI (init→scan, check→audit, benchmark) tapi bagian segfault salah diagnosa. CI log (run 29244152939) menunjukkan crash BUKAN stack overflow — ulimit -s unlimited tidak berpengaruh:

Fatal Python error: Segmentation fault
Current thread ... File "scripts/parsers/python_parser.py", line 126 in extract_references
  File "tests/test_large_file_parsing.py", line 119 in test_file_above_old_threshold_is_parsed
Extension modules: ... tree_sitter_python._binding
Segmentation fault (core dumped) python -m pytest ...

Crash native di tree_sitter_python._binding, dipicu file shallow 250-baris (bukan yang deeply-nested).

Root cause

• CI (segfault): tree-sitter core 0.26.0 (unpinned via tree-sitter>=0.21.0)
• Lokal (lolos): tree-sitter core 0.25.2

python_parser.py sendiri sudah punya komentar bahwa "tree-sitter 0.26's binding does not make Node objects hold a strong reference to the Tree" — mitigasi keep_alive-nya tidak cukup untuk 0.26 → native use-after-free.

Perbaikan

Pin tree-sitter>=0.21.0,<0.26 (versi 0.25.x known-safe) di:

• pyproject.toml (source of truth)
• codelens-ci.yml (3 job), codelens-benchmark.yml, codelens-sarif.yml

Revert ulimit yang menyesatkan (hipotesis salah).

Follow-up

Issue baru akan dibuat: buat python_parser.py keep_alive strategy 0.26-safe supaya cap bisa dilepas. Itu deep parser work → worker.

Closes #235

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud