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>

.forgejo/workflows/ci.yaml

@@ -21,7 +21,7 @@ jobs:
       FLUTTER_VERSION: 3.47.5
       # The Serverpod CLI, for the generated-code check: the server's Serverpod version
       # (the root pubspec's overrides); move it together with them.
-      SERVERPOD_VERSION: 4.0.3
+      SERVERPOD_VERSION: 4.0.4
     steps:
       # Before anything else runs, the job proves it can neither see nor reach production
       # (the runner's sandbox, deploy/runner/). If it can, nothing else should run.