ci: wait for job-service to be ready before running e2e tests

The job-service has its own retry loop to connect to postgres and may not
be ready immediately after the DB setup job completes. This caused race
conditions where tests would timeout waiting for jobs that the job-service
hadn't started processing yet.

Add a step to wait for the "starting jobs service" log message before
running e2e tests.

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

Author: theothersideofgod

.github/workflows/test-k8s-deployment.yaml

@@ -139,6 +139,19 @@ jobs:
           kubectl wait --for=condition=complete job/constructive-db \
             -n constructive-functions --timeout=180s
 
+      - name: Wait for job-service to be ready
+        run: |
+          echo "Waiting for job-service to start processing jobs..."
+          for i in {1..30}; do
+            if kubectl logs -n constructive-functions -l app=knative-job-service --tail=50 2>/dev/null | grep -q "starting jobs service"; then
+              echo "Job-service is ready!"
+              break
+            fi
+            echo "  Attempt $i/30: job-service not ready yet..."
+            sleep 2
+          done
+          kubectl logs -n constructive-functions -l app=knative-job-service --tail=20
+
       - name: Port-forward postgres and run e2e tests
         env:
           PGHOST: localhost