Properly fix waiting for dependencies

[jmezach]

**Closes #942 **

This should fix the waiting for dependent resources.

PR Checklist

• Created a feature/dev branch in your fork (vs. submitting directly from a commit on main)
• Based off latest main branch of toolkit
• PR doesn't include merge commits (always rebase on top of our main, if needed)
• New integration
  • Docs are written
  • Added description of major feature to project description for NuGet package (4000 total character limit, so don't push entire description over that)
• Tests for the changes have been added (for bug fixes / features) (if applicable)
• Contains NO breaking changes
• Every new API (including internal ones) has full XML docs
• Code follows all style conventions

Other information

[Copilot]

Pull Request Overview

This PR fixes the dependency waiting mechanism for SQL Database Projects by implementing proper waiting for dependencies before attempting to publish a SQL project. Previously, the publish operation may have proceeded without ensuring required resources were ready.

Key Changes:

• Added explicit waiting for dependencies using WaitForDependenciesAsync when the target is a SqlServerDatabaseResource
• Implemented handling of WaitAnnotation to wait for specific resource states based on WaitType
• Ensures all waiting tasks complete before proceeding with dacpac publishing

[Copilot]

If waitingTasks is empty, Task.WhenAll will return immediately, which is correct behavior. However, if the target is not a SqlServerDatabaseResource and there are no wait annotations, this may proceed without waiting for any dependencies when it should. Consider whether waiting should be mandatory for all resource types.

[jmezach]

Looks like this is being hit by #974 as well

[ErikEJ]

@jmezach Great - ran my repro locally, and can confirm that this finally works as expected now

[ErikEJ]

I will test this with #529 as well!

[aaronpowell]

When I run the sample app I see a bunch hanging:

This is why the tests time out.

Logs on the database show this:

Maybe something is causing db restores to fail that is then cascading elsewhere?

[jmezach]

Closing this in favor of #994