test(e2e): mark the heavy share-lifecycle and med-wizard flows slow

Both are legitimately long end-to-end flows — the share test spans two
browser contexts (owner create + picker, recipient unlock, multiple
document serves, revoke), and the med wizard gates its Next button on
per-step validation. On a loaded CI runner the default 30s timeout races
the settle; test.slow() triples it so transient runner contention stops
flaking green flows.

e2e/medications-wizard-daily.spec.ts

@@ -29,6 +29,10 @@ test.describe("medication wizard — daily", () => {
   test.use({ storageState: STORAGE_STATE_PATH });
 
   test("creates a daily medication end-to-end", async ({ page }) => {
+    // Multi-step wizard with per-step validation gating the Next button;
+    // under a loaded CI runner the validation settle can lag the default
+    // 30s, so this legitimately-long flow earns the tripled timeout.
+    test.slow();
     await stubDashboardAnalytics(page);
     const capture = mockMedicationsApi(page, {
       id: STUB_MEDICATION_ID,

e2e/share-documents.spec.ts

@@ -136,6 +136,11 @@ test.describe("clinician document sharing", () => {
     page,
     browser,
   }) => {
+    // A full lifecycle across two browser contexts (owner create + picker,
+    // recipient unlock, several document serves, revoke): legitimately heavy,
+    // so it earns the tripled timeout rather than racing the default 30s on a
+    // loaded CI runner.
+    test.slow();
     const share = await createShareWithDocs(page);
     const clinician = await openUnlockedClinician(browser, share);