Prevent liveness probes causing dev to think something is healthy immediately

[TylerAldrich]

https://gitlab.com/architect-io/architect-cli/-/issues/630

The serverStatus object has a key with the service IP/port and a status like 'UP'. When there's a liveness probe and it's failing, it looks like this:

  serverStatus: { '': 'UP' },

so we incorrectly said it was healthy just because UP existed. But, UP exists because we tell traefik allowEmptyServices now.

Once the service has URL:

  serverStatus: { 'http://172.18.0.2:8080': 'UP' },

the liveness probe actually passed and we can now say it's healthy and open links in the browser.

[github-actions[bot]]

:tada: This PR is included in version 1.35.0 :tada:

The release is available on:

• v1.35.0
• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot :package::rocket: