WaitFor for Azure Storage

[mitchdenny]

Description

Adding WaitFor(...) support for Azure Storage. This one ended up being a bit more involved than normal because Azure storage is one of the few resources that has a parent resource that does not have a connection string, whereas child resources do.

To make this work I've centralized propagation of the ConnectionStringAvailableEvent events for child resource and removed it from the extension methods for each resource.

Fixes #5645

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
    • Link to aspire-docs issue:
  • No

Microsoft Reviewers: Open in CodeFlow

[mitchdenny]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[davidfowl]

Do you need this still?

[mitchdenny]

Yes we still have resources that depend on it (Postgres/Redis etc).