fix(doctor-report): take the day path for dense heart-rate variability and blood oxygen

The report's dense exception covered pulse and glucose. Heart-rate
variability and blood oxygen were read raw for any window, and a watch
or ring writing them every minute puts six figures of readings into a
long report that draws them as one sparkline.

Their report sections are a statistics row and a series, the same as
pulse, so they take the same rule: beyond 90 days per local day, and
inside 90 days per local day once the window holds more than 10 000 of
their readings. One grouped count decides each type on its own. Count,
minimum, maximum and the latest reading stay exact; the mean is the
readings' mean. Glucose keeps its own rule because its clinical panel
needs the per-reading counts.

The bucket query now takes a list of types instead of two flags.

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

@@ -19,8 +19,12 @@ import { unzipSync } from "fflate";
 
 vi.mock("@/lib/db", () => ({
   prisma: {
-    // `count` sizes the report's pulse window (#1023): a sparse account.
-    measurement: { findMany: vi.fn(), count: vi.fn(async () => 0) },
+    // `groupBy` sizes the report's dense windows (#1023): a sparse account.
+    measurement: {
+      findMany: vi.fn(),
+      count: vi.fn(async () => 0),
+      groupBy: vi.fn(async () => []),
+    },
     medication: { findMany: vi.fn() },
     medicationIntakeEvent: { findMany: vi.fn() },
     moodEntry: { findMany: vi.fn() },