Move test jobs to VPS runner, keep deploy on NAS

Backend and frontend tests now run on `runs-on: vps` (server2 at
158.101.140.85, host mode) with checkout via Tailscale IP. Deploy
job stays on `runs-on: nas` with gitea_gitea network for Docker
socket access. This eliminates the HDD bottleneck and Docker
network/DNS issues that plagued the all-NAS pipeline.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

.gitea/workflows/deploy.yml

@@ -14,9 +14,7 @@ concurrency:
 jobs:
   backend-tests:
     name: Backend Tests
-    runs-on: ubuntu-latest
+    runs-on: vps
-    container:
-      network: gitea_gitea
     env:
       SECRET_KEY: test-secret-key-for-ci-environment-32chars-minimum
 
@@ -24,7 +22,7 @@ jobs:
       - name: Checkout repository
         run: |
           if [ ! -d .git ]; then
-            git clone --depth=1 "http://gitea:3000/${GITHUB_REPOSITORY}.git" .
+            git clone --depth=1 "http://100.78.131.124:3300/${GITHUB_REPOSITORY}.git" .
           fi
 
       - name: Setup Python
@@ -104,15 +102,13 @@ jobs:
 
   frontend-tests:
     name: Frontend Tests
-    runs-on: ubuntu-latest
+    runs-on: vps
-    container:
-      network: gitea_gitea
 
     steps:
       - name: Checkout repository
         run: |
           if [ ! -d .git ]; then
-            git clone --depth=1 "http://gitea:3000/${GITHUB_REPOSITORY}.git" .
+            git clone --depth=1 "http://100.78.131.124:3300/${GITHUB_REPOSITORY}.git" .
           fi
 
       - name: Setup Node.js
@@ -174,7 +170,7 @@ jobs:
 
   deploy:
     name: Deploy to Production
-    runs-on: ubuntu-latest
+    runs-on: nas
     if: always()
     needs: [backend-tests, frontend-tests]
     env: