bug: starship-cli, wait-for-pods exists quickly after Running state

[Anmol1696]

Overview

Currently, the starship wait-for-pods (so also start) command exists quickly after getting all pods in Running state, which could be a bug.

Example: https://github.com/cosmology-tech/starship/actions/runs/9504181248/job/26225850829

Proposal

We need to:

• give it more time to recover: pods seem to self heal as well after 1 or 2 crashlookbackoff
• check for running state for longer, 5-10secs to make sure everything is up and running
• proper exit if things did not run as usual

Note: Even if the Status: Running is achived by the pods, the Ready state need to be checked to make sure the installation is done properly.

[Anmol1696]

Here as well, we can see: https://github.com/cosmology-tech/starship/actions/runs/9514253431/job/26226066554?pr=476

The pods are in Running state but not ready. Need to check for it.