feat: add comprehensive testing mechanism for dashboard features

- Add smoke test script for post-deployment verification
- Add health monitoring script with Telegram alerts
- Add backend integration tests for conversation tracker API
- Add frontend tests to verify correct API paths
- Update CI/CD workflows to enforce test failures and run smoke tests
- Add comprehensive testing documentation

This testing mechanism will catch issues like the double /api/ prefix bug
before they reach users.

.gitea/workflows/deploy-dev.yml

@@ -80,3 +80,31 @@ jobs:
           # Manually connect to networks after container is created
           docker network connect nas-dashboard_internal nas-dashboard-dev || true
           docker network connect gitea_gitea nas-dashboard-dev || true
+      - name: Wait for container to be healthy
+        run: |
+          echo "Waiting for container to be healthy..."
+          for i in {1..30}; do
+            STATUS=$(docker inspect --format='{{.State.Health.Status}}' nas-dashboard-dev 2>/dev/null || echo "starting")
+            if [ "$STATUS" = "healthy" ]; then
+              echo "Container is healthy"
+              break
+            fi
+            echo "Waiting... ($i/30) Status: $STATUS"
+            sleep 2
+          done
+          # Final check
+          STATUS=$(docker inspect --format='{{.State.Health.Status}}' nas-dashboard-dev 2>/dev/null || echo "unknown")
+          if [ "$STATUS" != "healthy" ]; then
+            echo "Container failed to become healthy: $STATUS"
+            docker logs nas-dashboard-dev --tail 50
+            exit 1
+          fi
+      - name: Run smoke tests
+        run: |
+          cd /volume1/repos/nas-tools
+          bash scripts/smoke-test-dashboard.sh dev
+          if [ $? -ne 0 ]; then
+            echo "Smoke tests failed! Check logs above."
+            docker logs nas-dashboard-dev --tail 100
+            exit 1
+          fi