[API Server] API Server restart after Pod recreation in Helm deployment

[aylei]

$ kubectl logs -p skypilot-api-service-7696657ff-mw6pc
Defaulted container "skypilot-api" out of: skypilot-api, create-aws-credentials (init), setup-gcp-credentials (init)
Pre-deploy hook
Failed to connect to SkyPilot API server at http://0.0.0.0:46580. Starting a local server.
sky.exceptions.ApiServerConnectionError: Could not connect to SkyPilot API server at http://127.0.0.1:46580. Please ensure that the server is running. Try: curl http://127.0.0.1:46580/api/health

During handling of the above exception, another exception occurred:

RuntimeError: Failed to start SkyPilot API server at http://0.0.0.0:46580
View logs at: ~/.sky/api_server/server.log

1. the log should be tailed for diagnosis
2. startup check can be skipped in helm deployment, since the readiness-probe and liveness-probe do the same work and are tunable for operators