fix(amazonq): fixed bug with high CPU use event loop for security scan findings

[mr-lee]

Problem

Opening the security scan issues webview led to an infinite loop on the update call, consuming significant amounts of customer CPU.

Solution

Updated the webview to not auto-update, and made it so that each "view" command opened a new window, even if already present.

This isn't fully ideal, but it at least immediately fixes the CPU consumption issue. Any setup to watch/poll for updates from the server would be either expensive or latent. This will be the most clean, but may lead to a different UX than expected.

---

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.
• This pull request implements a feat or fix, so it must include a changelog entry (unless the fix is for an unreleased feature). Review the changelog guidelines.
  • Note: beta or "experiment" features that have active users should announce fixes in the changelog.
  • If this is not a feature or fix, use an appropriate type from the title guidelines. For example, telemetry-only changes should use the telemetry type.

[jpinkney-aws]

looks good from my side, still needs an additional review from the security scan team