fix: Serverpod v4.0.4 and serverpod_offline_sync v0.0.10

serverpod_offline_sync v0.0.10 collects outbound changes in one
consistent snapshot, so a sync no longer fails on writes made while it
runs (upstream #84, #163), keeps checkpoints per author, so a device
clock moving backwards no longer stalls sync or resends data, and keeps
unique conflicts and foreign key defaults alike on every device. Its
tables and its messages are unchanged: no migration, and apps on v0.0.8
keep syncing. It needs Serverpod >=4.0.4 <4.1.0 (v4.0.4 is fixes only),
so the root overrides that held the workspace on one Serverpod go: each
package pins v4.0.4 itself. The generated code is identical under the
v4.0.4 CLI, which CI now uses.

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

pubspec.yaml

@@ -15,16 +15,3 @@ workspace:
 dev_dependencies:
   # Referenced by analysis_options.yaml in this directory.
   leancode_lint: ^27.0.0
-
-# serverpod_offline_sync v0.0.8 pins Serverpod v4.0.0 exactly. The sync spike showed the
-# pin is conservative (serverpod_database v4.0.0 and v4.0.2 have identical lib/, and sync
-# works on v4.0.2), so these four keep the whole workspace on the Serverpod we run. Every
-# Serverpod upgrade re-checks them until the package widens its constraints (ADR 0001).
-# v4.0.3 checked: serverpod_database only gained backwards-compatible changes (custom SQL
-# defaults tolerated, an optional ignoreDefault on column comparison, a laxer integrity
-# check for unmanaged tables), none of which the sync package calls into.
-dependency_overrides:
-  serverpod: 4.0.3
-  serverpod_client: 4.0.3
-  serverpod_database: 4.0.3
-  serverpod_serialization: 4.0.3