[FEAT] Reflect unhealthy providers in application status

[brooksmtownsend]

The Provider spreadscaler + daemonscalers currently handle provider_start_failed events to update application status based on application level events. We should extend this handling to also include health_check_failed events and health_check_succeeded in order to reflect when an application is unhealthy.

We could start this feature using the existing Failed status to reflect the issue, but we may want to add an Unhealthy status to indicate that the application was scheduled/deployed but with problems.

See https://wasmcloud.com/docs/reference/cloud-event-list#health_check_passed for the event specifications.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If this has been closed too eagerly, please feel free to tag a maintainer so we can keep working on the issue. Thank you for contributing to wasmCloud!

[Vikrantpalle]

Hey, I would like to have a go at this issue.