Update WaitForResourceHealthyAsync to use DefaultWaitBehavior

[afscrome]

Description

Follow on to #7650 - this changes makes the default behaviour if you call WaitForResourceHealthyAsync without a WaitBehavior to use DefaultWaitBehavior rather than hardcode WaitOnResourceUnavailable.

This makes the behaviour match WaitForDependenciesAsync when WaitFor is called without a WaitBehavior, as well as improving the testing (or other dashboardless) experience by making WaitForResourceHealthyAsync fail fast in tests when you don't have a way to recover resources if they fail, without needing to explicitly set the WaitBehavior

If this change is not wanted, the default test templates should be updated to include WaitBehavior.StopOnResourceUnavailable as a follow on to #7619

- await app.ResourceNotifications.WaitForResourceHealthyAsync(dependency.Resource.Name).WaitAsync(TimeSpan.FromSeconds(15));
+ await app.ResourceNotifications.WaitForResourceHealthyAsync(dependency.Resource.Name, WaitBehavior.StopOnResourceUnavailable).WaitAsync(TimeSpan.FromSeconds(15));

Fixes #7601

(Pushing this as is to see if any tests break and need adapting to this change in defaults - if any do, I'm expecting them to be tests deep in aspire internals that are unlikely to affect real end user usage, but need to confirm.)

Update: Only one test failed first time, but it passes locally and succeeded on the second run

Checklist

• Is this feature complete?
  • Yes. Ready to ship.
  • No. Follow-up changes expected.
• Are you including unit tests for the changes and scenario tests if relevant?
  • Yes
  • No
• Did you add public API?
  • Yes
    • If yes, did you have an API Review for it?
      • Yes
      • No
    • Did you add <remarks /> and <code /> elements on your triple slash comments?
      • Yes
      • No
  • No
• Does the change make any security assumptions or guarantees?
  • Yes
    • If yes, have you done a threat model and had a security review?
      • Yes
      • No
  • No
• Does the change require an update in our Aspire docs?
  • Yes
    • Is this introducing a breaking change?
      • Yes
        • Link to aspire-docs issue (please use this breaking-change template):
      • No
        • Link to aspire-docs issue (please use this doc-idea template):
  • No

[mitchdenny]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[mitchdenny]

Rerunning all jobs just to verify that this is compatible with all latest changes and then I'll merge in.

[mitchdenny]

/backport to release/9.1

[github-actions]

Started backporting to release/9.1: https://github.com/dotnet/aspire/actions/runs/13467677933