fix: sync package.runtime.json version in Docker builds (v2.33.1) (#534)

Docker images were built with stale package.runtime.json (v2.29.5)
while npm package was at v2.33.0. This was caused by the build-docker
job not syncing the version before building, while publish-npm did.

Changes:
- Add "Sync runtime version" step to release.yml build-docker job
- Add "Sync runtime version" step to docker-build.yml build job
- Add "Sync runtime version" step to docker-build.yml build-railway job
- Bump version to 2.33.1 to trigger release with fix

The sync uses a lightweight Node.js one-liner (no npm install needed)
to update package.runtime.json version from package.json before
Docker builds.

Conceived by Romuald Czlonkowski - www.aiadvisors.pl/en

Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>

.github/workflows/release.yml

@@ -427,7 +427,18 @@ jobs:
             exit 1
           fi
           echo "✅ Sufficient disk space: ${AVAILABLE_GB}GB available"
-      
+
+      - name: Sync runtime version for Docker
+        run: |
+          VERSION=$(node -p "require('./package.json').version")
+          node -e "
+            const fs = require('fs');
+            const pkg = JSON.parse(fs.readFileSync('package.runtime.json'));
+            pkg.version = '$VERSION';
+            fs.writeFileSync('package.runtime.json', JSON.stringify(pkg, null, 2) + '\n');
+          "
+          echo "✅ Synced package.runtime.json to version $VERSION"
+
       - name: Set up QEMU
         uses: docker/setup-qemu-action@v3