docs: aggregate clinician review questions for Turkish clinician validation

[aerenkaradag]

What

Adds docs/clinical-review/clinician_review_questions_tr.md — a single, trackable
table that consolidates the clinical-validation needs scattered across the
help-wanted-clinician issues (open and closed) plus a few clinical
assumptions found only in code.

The document is structured as:

• Bölüm 1 — Hekim-facing tablo (plain Turkish, minimal jargon): the questions a
  Turkish clinician should answer, with the system's current assumption stated for
  each. Multi-part issues ([clinical-curation] Author a CKD-staging module (eGFR-driven, G1-G5) #17, [clinical-curation] Increase ICD-10 specificity (.9 unspecified -> specified forms) #19) are split into separate rows so each question
  gets its own answer cell.
• Bölüm 2 — Code-derived needs: clinical assumptions present in code without a
  tracking issue (thyroid auto-hypothyroid, diabetes insulin trigger,
  anxiety+depression drug choice, hyperlipidemia LDL≥190 rule).
• Bölüm 3 — Developer traceability table (English): issue → PR → code path →
  action → priority → status.
• Ek A — Türkçe Klinik Terim Listesi: the full CONDITION_DISPLAY_TR term list
  with empty cells for the clinician to mark each term (Issue [clinical-curation] Verify Turkish display strings against Türk Tabipleri Birliği convention #20).

Why

The clinician-facing validation questions were spread across individual issues and
PR comments. This moves them into one auditable document so the Turkish-clinician
review process is easier to follow and track.

Important

• Doctor answers are intentionally left blank. No clinical content has been
  invented or guessed.
• This PR does not produce clinical validation answers — it only collects the
  questions and their context.
• After a clinician fills in answers, the relevant clinical modules, FHIR mappings,
  reference ranges, medication logic, and/or manuscript statements will be updated
  in follow-up PRs.

Note on #17

The CKD module (#17) was merged via #46 without the clinical-confirmation
checklist being signed off (the PR has no review). Its open clinical questions
(KDIGO cut-points, referral stage, ACR trigger, nephrotoxic-drug avoidance) are now
tracked in this aggregate document.

[codecov-commenter]

⚠️ Please install the to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

✅ All modified and coverable lines are covered by tests.
❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

@@          Coverage Diff          @@
##            main     #53   +/-   ##
=====================================
  Coverage   91.0%   91.0%           
=====================================
  Files         39      39           
  Lines       1602    1602           
=====================================
  Hits        1459    1459           
  Misses       143     143           

Flag	Coverage Δ
unittests	91.0% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.