fix(privacy): encrypt workout GPS tracks and practitioner contact details at rest

The GPS track of an outdoor workout was stored readable, and its first and
last points are usually the person's front door. The phone number and address
in the address book of doctors and practices were readable too, while the
note beside them was already encrypted.

Migration 0361 adds workout_routes.geometry_encrypted (the geometry loses
its NOT NULL) and practitioners.phone_encrypted / location_encrypted, plus
partial indexes on the backfill's discovery predicates. A track is sealed as
one binary AES-256-GCM value bound to its purpose; the contact fields use the
same Bytes codec as the note. The practitioner's name, practice and specialty
stay readable, because the picker searches and sorts on them.

Every writer stores ciphertext only: workout batch ingest, practitioner
create and edit, and both restore formats. Readers prefer the ciphertext and
fall back to the old column for rows not yet migrated: the workout detail
(map, splits, GPX), the activity insight's climb figure, the practitioner
DTO behind the address book, visits and vaccinations. The wire shape does not
change. An edit's audit row now names a changed phone number or address
without recording either value.

free-text-encryption-backfill covers the three columns in the same pass,
finding a route through its workout. All three are registered for key
rotation (registry, CLI script, and the in-app rotation). A disaster-recovery
backup carries the contact fields as ciphertext only; a portable export
carries them readable. Workout routes are still not part of a backup, as
before. The old columns are marked for removal in a later release.

scripts/rotate-encryption-key.ts

@@ -700,6 +700,35 @@ async function main() {
       prisma.practitioner,
     ),
   );
+  // v1.39.4 — the practice's phone number and address. NULL on a field the
+  // person left empty and on a row the free-text backfill has not reached
+  // yet; `rotateBytesColumn` skips both.
+  // "phoneEncrypted" "locationEncrypted"
+  results.push(
+    await rotateBytesColumn(
+      "Practitioner",
+      "phoneEncrypted",
+      prisma.practitioner,
+    ),
+  );
+  results.push(
+    await rotateBytesColumn(
+      "Practitioner",
+      "locationEncrypted",
+      prisma.practitioner,
+    ),
+  );
+
+  // ───── v1.39.4 workout GPS track (Bytes, binary2, batched) ─────
+  // One sealed binary value per route, labelled for its purpose. Walked
+  // through the registry so the binary codec and the label are honoured, in
+  // id-cursor batches because a track can be close to a megabyte. NULL on a
+  // row the free-text backfill has not reached yet, which the walk skips.
+  results.push(
+    await rotateRegistryColumn("WorkoutRoute", "geometryEncrypted", {
+      workoutRoute: prisma.workoutRoute,
+    } as unknown as CorpusClient),
+  );
 
   // ───── v1.39.3 custom-metric reading note (Bytes column) ─────
   // NULL on a reading without a note, and on a row the free-text backfill has