Misleading UX when starting a service scalable to zero

[jvstme]

Steps to reproduce

Apply the configuration:

type: service
image: nginx
port: 80
replicas: 0..1
scaling:
  metric: rps
  target: 1

Actual behaviour

Until the first request hits the service, the following is displayed in the CLI:

⠴ Launching srv...
 NAME  BACKEND  RESOURCES  PRICE  STATUS   SUBMITTED  
 srv                              pending  2 mins ago

The "Launching" spinner and the lack of a service URL mislead users into thinking the service hasn't been created yet.

Expected behaviour

1. Show the service URL once the service is created, even before it is scaled to one replica.
2. Instead of "Launching", show a more relevant message/spinner, such as "Waiting for requests"

dstack version

0.19.24

Server logs

Additional information

No response