fix(ci): resolve SSH hostname resolution issue in Gitea deployment

- Replace ssh-keyscan with SSH config to avoid DNS lookup
- Disable StrictHostKeyChecking for automated deployment
- Fix cleanup step order to execute SSH command before removing key
- Use IP address directly from SYNOLOGY_HOST secret

🤖 Generated with [Claude Code](https://claude.com/claude-code)

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

.gitea/workflows/deploy-synology.yml

@@ -160,7 +160,13 @@ jobs:
           mkdir -p ~/.ssh
           echo "${{ secrets.SYNOLOGY_SSH_KEY }}" > ~/.ssh/synology_key
           chmod 600 ~/.ssh/synology_key
-          ssh-keyscan -H ${{ secrets.SYNOLOGY_HOST }} >> ~/.ssh/known_hosts
+          # Disable strict host key checking for deployment
+          cat >> ~/.ssh/config << 'EOF'
+          Host *
+            StrictHostKeyChecking no
+            UserKnownHostsFile /dev/null
+          EOF
+          chmod 600 ~/.ssh/config
 
       - name: Copy Files to Synology
         run: |
@@ -208,10 +214,12 @@ jobs:
       - name: Cleanup
         if: always()
         run: |
-          rm -f ~/.ssh/synology_key
+          # Remove Docker image from Synology
           ssh -i ~/.ssh/synology_key \
             ${{ secrets.SYNOLOGY_USER }}@${{ secrets.SYNOLOGY_HOST }} \
             "rm -f /volume1/docker/laravel-app/laravel-app.tar.gz" || true
+          # Remove SSH key
+          rm -f ~/.ssh/synology_key
 
   # Job 4: Notify on Success/Failure (optional)
   notify: