Propogate errors to the users that prevent webserver or scheduler to start

[sunkickr]

Describe the bug

If the webserver or scheduler get stuck in a starting state the user doesn't know

Use 'docker scan' to run Snyk tests against images to find vulnerabilities and learn how to fix them
Env file ".env" found. Loading...
[+] Running 4/4
 ⠿ Container example-repo-update_e4e3a9-postgres-1   Started                                                                                                                                           1.2s
 ⠿ Container example-repo-update_e4e3a9-scheduler-1  Started                                                                                                                                           2.4s
 ⠿ Container example-repo-update_e4e3a9-triggerer-1  Started                                                                                                                                           2.4s
 ⠿ Container example-repo-update_e4e3a9-webserver-1  Started                                                                                                                                           3.2s

Airflow is starting up! This might take a few minutes…

What CLI Version did you experience this bug?

1.6

What Operating System is the above CLI installed on?

🪜 Steps To Reproduce

1. use astro-sdk in dag
2. set AIRFLOWCOREENABLE_XCOM_PICKLING=FALSE
3. astro dev start

📸 Screenshots

[sunkickr]

A few ideas here:

• 5 min timeout on the webserver health status check
• have a max number of pod retries for the scheduler and webserver (maybe 3 retries)