[Bug]: Run/job status in UI/CLI is shown as provisioning instead of pulling

[peterschmidt85]

Fixes #2830

[jvstme]

For multi-job runs, it can be misleading to rely solely on the status of the first job.

Consider a two-replica service. If the first replica is pulling and the second is running, the current implementation will set the run status message to pulling.

 NAME               BACKEND          RESOURCES                        PRICE    STATUS   SUBMITTED  
 test-service                                                                  pulling  3 mins ago 
   replica=0 job=0  aws (us-west-2)  cpu=2 mem=1GB disk=100GB (spot)  $0.0025  pulling  21 sec ago 
   replica=1 job=0  aws (us-west-2)  cpu=2 mem=1GB disk=100GB (spot)  $0.0025  running  3 mins ago

However, if the first replica is running and the second is pulling, the message will be running.

 NAME               BACKEND          RESOURCES                        PRICE    STATUS   SUBMITTED  
 test-service                                                                  running  8 mins ago 
   replica=0 job=0  aws (us-west-2)  cpu=2 mem=1GB disk=100GB (spot)  $0.0025  running  6 mins ago 
   replica=1 job=0  aws (us-west-2)  cpu=2 mem=1GB disk=100GB (spot)  $0.0025  pulling  16 sec ago

This inconsistency is misleading because the replicas are supposed to have equal importance.

I can suggest to only rely on the job status for single-job runs. In multi-job runs, job statuses will not affect the run status message.

Suggested change

	job_status = (
	jobs[0].job_submissions[-1].status if jobs and jobs[0].job_submissions else None
	)
	job_status = (
	jobs[0].job_submissions[-1].status
	if len(jobs) == 1 and jobs[0].job_submissions
	else None
	)

[peterschmidt85]

Sorry, merged without! Will fix separately!