Fix docker-compose to use Gitea registry image; v1.1.41

docker-compose.yml was still pointing to the old GHCR image
(ghcr.io/nmemmert/siteforge:latest) after CI was switched to push
to git.necloud.us/nate/siteforge:latest, so servers were pulling
a stale build that predated the download/header changes.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

docker-compose.yml

@@ -1,6 +1,6 @@
 services:
   portfolio:
-    image: ghcr.io/nmemmert/siteforge:latest
+    image: git.necloud.us/nate/siteforge:latest
     pull_policy: always
     container_name: siteforge-app
     ports:

package.json

@@ -1,7 +1,7 @@
 {
   "name": "siteforge",
   "private": true,
-  "version": "1.1.40",
+  "version": "1.1.41",
   "type": "module",
   "scripts": {
     "dev": "vite",