Should not enable port before tidb starts successfully

## Enhancement

Issue source:
https://asktug.com/t/topic/663316
For the issue mentioned in the above topic, the user used tiup to start the tidb cluster. TiUP kept trying the port 4000 after the "start" commend, and TiUP would show "Started cluster `liking` successfully" when the port is accessible. In the above case,actually the cluster failed to start ,but it enabled the port (4000) . TiUP can access the port, then it showed "Started cluster successfully" which was misleading .

Expected behavior:
Tidb should not make the port accessible before it really start successfully.