verifyServerUrl does not work with new startup methods

[dblythy]

New Issue Checklist

• I am not disclosing a vulnerability.
• I am not just asking a question.
• I have searched through existing issues.
• I can reproduce the issue with the latest version of Parse Server.

Issue Description

verifyServerUrl does not respect the starting state, and can log an error when the server is starting up.

Steps to reproduce

Use new startup method, and call verifyServerUrl.

Actual Outcome

Logs "unable to connect to xxx, cloud code may not be available"

Expected Outcome

verifyServerUrl should consider startup environment

Environment

Server

• Parse Server version: alpha
• Operating system: macos
• Local or remote host (AWS, Azure, Google Cloud, Heroku, Digital Ocean, etc): local

Database

• System (MongoDB or Postgres): mongo
• Database version: 5
• Local or remote host (MongoDB Atlas, mLab, AWS, Azure, Google Cloud, etc): atlas

Client

• SDK (iOS, Android, JavaScript, PHP, Unity, etc): n/a
• SDK version: n/a

Logs

[parse-github-assistant]

Thanks for opening this issue!

• 🚀 You can help us to fix this issue faster by opening a pull request with a failing test. See our Contribution Guide for how to make a pull request, or read our New Contributor's Guide if this is your first time contributing.

[parseplatformorg]

🎉 This change has been released in version 6.0.0-alpha.22

[parseplatformorg]

🎉 This change has been released in version 6.0.0-beta.1

[parseplatformorg]

🎉 This change has been released in version 6.0.0