feat(train): weight, entered on Progress and read from Health Connect, sealed and synced (ADR 0030, D63)

A person's weights are each a sealed `body_weight` row, as the days and
the places: the weight in grams, when it was measured (UTC), where it
came from and, for Health Connect's, the record's id and app are the
payload; the server sees the space and the ciphertext alone.

Progress gets a Weight card after Your body: the latest and its day,
its line over time (held, each weight and its day), the plus to enter
one (a comma taken as a point, 20 to 400 kg, when measured, today by
default) and All, the list to delete one. The latest weight is also
Your body's, which the band's and the zones' figures work from. In
kilograms alone: Train is metric throughout and has no units setting
yet.

Health Connect's weight records are read in when switched on in its
screen (READ_WEIGHT, asked as the others): each record once, its id kept
in health_connect.json also after it is deleted here, never Train's own,
and none within 10 minutes and 0.1 kg of a weight entered in Train.

The migration (20261103204323683-body-weights):
- creates (or replaces, unchanged) `gen_random_uuid_v7()`, the
  default of every UUID id, as each of Serverpod's migrations does;
- CREATE TABLE "body_weight": "id" uuid primary key defaulting to a
  UUID v7, "spaceId" bigint (the sync space), "keyId" text (the key
  that sealed it), "payload" bytea NOT NULL (the sealed content),
  "nonce" bytea;
- CREATE INDEX "body_weight_space_idx" on "spaceId", for a space's
  rows as the sync reads them;
- a foreign key from "spaceId" to "offline_sync_spaces"("id"),
  ON DELETE CASCADE, so that an account's deletion takes its weights
  with its space;
- the version rows of Train's and every module's migrations.
Nothing existing changes, so nothing is lost.

Tests: the row written and read back in its owner's space, and the
denials: another person reads none of them, and writing one into
another's space throws OfflineSyncSpaceMembershipException and leaves
it empty; an account's deletion takes them.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Tizian 「ティツィアーン」 <raisondetredev@pm.me>

apps/train/halkyon_train_server/lib/src/weight/body_weight.spy.yaml

@@ -0,0 +1,19 @@
+### A weight the person measured (ADR 0030, D63): when, how heavy and where
+### it came from (entered in Train, or read from Health Connect with that
+### record's ID, so that it is read once), in its sealed payload (D7); the
+### instance sees that it exists, its size and when it changed. A row each
+### measurement. Synced.
+class: BodyWeight
+table: body_weight
+database: sync
+fields:
+  ### The key it is sealed with (ADR 0002's envelope); never null in Train.
+  keyId: String?
+  ### The content, sealed: UTF-8 JSON with a `schemaVersion` once opened.
+  payload: ByteData
+  ### The sealing's nonce (ADR 0002's envelope).
+  nonce: ByteData?
+indexes:
+  # Deleting a space finds its rows through this index (see content_key).
+  body_weight_space_idx:
+    fields: spaceId