Decouple hiddenness in the dashboard from the resource state

[davidfowl]

We use the resource state as more than a visual indicator and that makes hidden resource a bit of a hack. It's especially a hack when we need to handle potential calls to wait for when a resource is hidden. It's sort of a terminal state but it's not. Instead we should decouple the hidden resource in the dashboard from the state of the resource.

We should also allow showing hidden resources.

cc @JamesNK @adamint

[afscrome]

Related to #6138 .

[mitchdenny]

This bit me today. I introduced a change to wait on the dashboard to start running before the Aspire CLI returned the dashboard URL on the console. Works inside our repo because we don't hide the dashboard in the resource list - but we do in the released packages. 🤦

[davidfowl]

@adamint do you have cycles to look at this?

[DamianEdwards]

My plan for implementing devtunnels support involves dormant hidden resources that become unhidden when a custom command is invoked, so I'm very interested in how we model hidden/visible resources too.