fix(amazonq): respond in chat right away when user enters JDK path

[dhasani23]

Problem

On a VS Code instance backed by CloudFront, when users enter their JDK path, it takes our chat 30+ seconds to respond.

Solution

Send a notification just before the build starts to also allow the other multiple chat messages to be sent.

---

• Treat all work as PUBLIC. Private feature/x branches will not be squash-merged at release time.
• Your code changes must meet the guidelines in CONTRIBUTING.md.
• License: I confirm that my contribution is made under the terms of the Apache 2.0 license.

[github-actions]

• This pull request modifies code in src/* but no tests were added/updated.
  • Confirm whether tests should be added or ensure the PR description explains why tests are not required.

[dhasani23]

Problem (on latest version of Q):

Screen.Recording.2024-12-18.at.2.38.20.PM.mov

Solution (this PR):

Screen.Recording.2024-12-18.at.2.39.47.PM.mov

[justinmk3]

Sleep for 0.5s to allow the JDK path to be processed (i.e. we make sure it exists)

So users on fast systems must always wait 500ms?

And, what happens on systems where it takes longer than 500ms?

[dhasani23]

We need this here anyway as an unrelated change, but still need to figure out a better solution besides sleeping for half a second

[dhasani23]

It looks like the few chat messages which should be showing up one-at-a-time before the copyProjectDependencies and installProjectDependencies functions below start, are actually showing up all at once after both of these functions complete. I guess that means these 2 functions are blocking the event loop, which is why adding a small delay before they begin provides enough time for the queued chat messages to send. Haven't been able to find another solution besides adding this delay.

Downsides are that it does delay for all users, and unclear if 500ms will always be enough of a delay.