Dashboard unclear when resource health checks have passed, but ResourceReady event has not completed

### Is there an existing issue for this?

- [x] I have searched the existing issues

### Describe the bug

If you have a resource with a Resource Ready event that hasn't completely processed, it can be a bit unclear from the dashboard as to why dependencies haven't started.

Take the following example, with `child.WaitFor(parent). With the Parent running and healthy, why is the child still waiting?

The only real way to tell is this line in the child's console output
> Waiting for resource ready to execute for 'parent'.

But I'm not sure that someone who doesn't understand the aspire resource model would really get what that means.

### Expected Behavior

If the Resource Ready Event hasn't fully processed, I think the resource should probably still be formatted the same way an "Unhealthy" resource does (i.e. running with a yellow tick).

Alternatively, some other kind of visual indication should be given.

### Steps To Reproduce

```cs
var parent = builder.AddContainer("parent", "nginx")
// Fake a long running ResourceReady subscriber
.OnResourceReady((_, _, ct) => Task.Delay(TimeSpan.FromDays(10), ct));

var child= builder.AddContainer("child", "nginx")
.WithParentRelationship(parent)
.WaitFor(parent);
```

### Exceptions (if any)

_No response_

### .NET Version info

_No response_

### Anything else?

_No response_