Allow the ResourceReadyEvent to block waiters

[davidfowl]

Description

When trying to write code that runs after a resource becomes healthy but before waiters are unblocked it requires complex coordination and a deep understanding of the resource lifecycle. This defaults to blocking waiters until the event is ready, allows users to build pretty nice experiences without complex coordination logic across resources.

Fixes #7164

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

[davidfowl]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[davidfowl]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[sebastienros]

runs after a resource becomes healthy but before waiters are unblocked

This is the reason I had to use a health check to seed the containers/dbs in the event hub host integration. With that I could move the logic there and use the standard health check.

[davidfowl]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[davidfowl]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[davidfowl]

I'm led to believe that this PR is either causing problems with these tests or exposing flakiness somewhere.