Improve start/stopping/restarting commands by waiting for completion

[JamesNK]

Description

• Resource start/stop/restart wait for a notification that the resource's state has changed to the desired state. For example, starting a resource causes the server to wait for a state of "Running".
• Timeout of 20 seconds and then a failure message is displayed.
• Fixed issue with displaying toast update in the dashboard. If a toast has closed then updating it does nothing. Now a toast is updated and its close time is extended if it is still open, or a new toast is shown with the update

Fixes #6224

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

Microsoft Reviewers: Open in CodeFlow

[JamesNK]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[davidfowl]

How did you pick this number?

[JamesNK]

I picked it myself. It seems like 20 seconds is a good amount of time for a timeout.

Edit: I added a comment to say how number was chosen.

[JamesNK]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).