feat(doctor-report): mark screener totals answered in an unvalidated translation

The report data counts, per screener score type, how many of the
window's results were answered in a translation that has not been
validated (`screenerUnvalidatedTranslations`, read only when a screener
total is in the report). The PDF marks such a row with an asterisk and
says under the vitals table how many of how many read as orientation;
the clinician share view says the same under the row.

To keep the aggregator and the PDF section from growing, the wellness
summary and the per-context glucose rows move into helpers; the size
ratchets only fall.

src/app/api/export/health-record/__tests__/route.test.ts

@@ -37,7 +37,12 @@ vi.mock("@/lib/db", () => ({
     userHealthProfile: { findUnique: vi.fn() },
     healthProfileFactRevision: { findMany: vi.fn() },
     // v1.43 — the anamnesis leaf also carries the newest AUDIT-C entry.
-    mentalHealthAssessment: { findMany: vi.fn(async () => []) },
+    // `groupBy` counts the screener totals answered in an unvalidated
+    // translation once a screener leaf is in the report.
+    mentalHealthAssessment: {
+      findMany: vi.fn(async () => []),
+      groupBy: vi.fn(async () => []),
+    },
     // v1.44 — the per-sport workout block.
     workout: { findMany: vi.fn(async () => []) },
     user: { findUnique: vi.fn(), update: vi.fn() },