🔧 Fix Gitea Actions for zero-downtime deployment

- Create new ci-cd-zero-downtime-fixed.yml workflow
- Disable old workflows that try to access port 3000 directly
- New workflow uses docker-compose.zero-downtime.yml
- Health checks now use nginx on port 80 instead of direct port 3000
- Fixes the 'Connection refused' errors in Gitea Actions

✅ Actions now properly work with zero-downtime nginx setup

scripts/monitor.sh

@@ -37,7 +37,7 @@ warning() {
 check_health() {
     log "Checking application health..."
     
-    if curl -f http://localhost:3000/api/health > /dev/null 2>&1; then
+    if curl -f http://localhost/api/health > /dev/null 2>&1; then
         success "Application is healthy"
         return 0
     else