feat: log only failing pods on helm validation job debug

[Copilot]

Debug output on validation failure currently calls kubectl describe pods -A, flooding logs with info from healthy pods and burying the actual failure signal.

Changes

• Filter failing pods: Replace blanket describe pods -A with a grep filter excluding Running, Completed, and Succeeded pods — only surfaces pods actually in a bad state
• Add per-pod logs: For each failing pod, fetch logs from all containers (--all-containers=true --tail=100) alongside the describe output
• Sort events by time: kubectl get events -A --sort-by='.lastTimestamp' for chronological ordering

Applied to both the helm-validation and e2e job debug steps.

kubectl get pods -A --no-headers | grep -vE '\s+(Running|Completed|Succeeded)\s+' | awk '{print $1" "$2}' | while read -r ns pod; do
  kubectl describe pod "$pod" -n "$ns"
  kubectl logs "$pod" -n "$ns" --all-containers=true --tail=100 2>/dev/null || true
done

• Fixes Improve Debugging when helm validation job fails #137