Fix IBM Power registry restart before push

Ensure local registry is running right before pushing custom kicbase image.
The registry may get cleaned up during the image build phase on shared CI machines.

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

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

Author: nammn

scripts/minikube/setup_minikube.sh

@@ -118,6 +118,21 @@ EOF
       echo "Failed to build custom image"
       return 1
     }
+
+    # Ensure registry is still running before push (may have been cleaned up during build)
+    if ! curl -s --max-time 2 http://localhost:5000/v2/_catalog >/dev/null 2>&1; then
+      echo "Registry not responding, restarting..."
+      sudo podman rm -f registry 2>/dev/null || true
+      sudo podman run -d -p 5000:5000 --name registry --restart=always docker.io/library/registry:2
+      for _ in {1..10}; do
+        if curl -s --max-time 2 http://localhost:5000/v2/_catalog >/dev/null 2>&1; then
+          echo "Registry restarted successfully"
+          break
+        fi
+        sleep 1
+      done
+    fi
+
     sudo podman push "${custom_image_tag}" --tls-verify=false || {
       echo "Failed to push to registry"
       return 1