feat(cycle): exclude disturbed temperatures from the symptothermal engine

A fever, illness, alcohol or a late/short-sleep reading can fake or mask
a temperature rise. Add a per-day `temperatureExcluded` flag on
CycleDayLog (migration 0156): when set, the engine drops the reading from
the cover-line baseline AND the shift evaluation, so a spike neither
fabricates nor masks a rise (Sensiplan: the cover line is drawn over the
last six unbracketed values).

Wired end to end — schema + Prisma, the engine's `detectTempShift`
filter, the Zod input/patch schemas, the day-log upsert (partial merge +
change detection), the read DTO, the calendar/insights/coach selects, the
backup round-trip, and the OpenAPI contract (a new boolean on the day-log
and calendar-day DTOs for the iOS client). The log-day sheet gains a
"mark reading as disturbed" toggle that appears once a temperature is
entered, translated across all six locales.

Citation: de.wikipedia "Symptothermale Methode"; myNFP "Temperaturkurve
auswerten" — Störfaktor bracketing.

src/lib/openapi/routes/cycle.ts

@@ -101,6 +101,7 @@ const cycleDayLogDto = z
     flow: flowLevelEnum.nullable(),
     intermenstrualBleeding: z.boolean(),
     basalBodyTempC: z.number().nullable(),
+    temperatureExcluded: z.boolean(),
     ovulationTest: ovulationTestEnum.nullable(),
     cervicalMucus: cervicalMucusEnum.nullable(),
     sexualActivity: z.boolean(),
@@ -175,6 +176,7 @@ const cycleCalendarDayDto = z.object({
   // so the web BBT chart renders from the calendar read (the values are already
   // loaded server-side for the symptothermal layer; no extra query).
   basalBodyTempC: z.number().nullable(),
+  temperatureExcluded: z.boolean(),
   ovulationTest: ovulationTestEnum.nullable(),
   cervicalMucus: cervicalMucusEnum.nullable(),
 });