fix: disable strict host key checking for homelab SSH

Homelab is on private network (192.168.0.109), so we can safely disable
strict host key checking. This avoids the complexity of managing known_hosts
entries in Gitea secrets.

Changes:
- Remove HOMELAB_SSH_KNOWN_HOSTS requirement
- Add -o StrictHostKeyChecking=no to scp/ssh commands
- Add -o UserKnownHostsFile=/dev/null to avoid host key persistence

.gitea/workflows/release.yaml

@@ -152,17 +152,20 @@ jobs:
           mkdir -p ~/.ssh
           printf '%s\n' "${{ secrets.HOMELAB_SSH_KEY }}" > ~/.ssh/homelab_key
           chmod 600 ~/.ssh/homelab_key
-          printf '%s\n' "${{ secrets.HOMELAB_SSH_KNOWN_HOSTS }}" >> ~/.ssh/known_hosts
 
       - name: Copy docker-compose.yml to homelab
         run: |
           scp -i ~/.ssh/homelab_key \
+            -o StrictHostKeyChecking=no \
+            -o UserKnownHostsFile=/dev/null \
             homelab/docker-compose.yml \
             "${{ secrets.HOMELAB_USER }}@${{ secrets.HOMELAB_HOST }}:/opt/libnovel-runner/docker-compose.yml"
 
       - name: Pull new runner image and restart
         run: |
           ssh -i ~/.ssh/homelab_key \
+            -o StrictHostKeyChecking=no \
+            -o UserKnownHostsFile=/dev/null \
             "${{ secrets.HOMELAB_USER }}@${{ secrets.HOMELAB_HOST }}" \
             'set -euo pipefail
              cd /opt/libnovel-runner