fix(amazonq): quick action handler should add to tab storage

[jpinkney-aws]

Problem

currently tabs get added to the tabs storage when the onTabAdd handler gets called.

In hybrid chat, the onTabAdd handler will never get called, because it first needs to be in the tabsStorage, which doesn't happen because the onTabAdd handler hasn't been called

Solution

in hybrid chat mode just add new tabs directly to the tabs storage

---

• 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.
• 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.

[Hweinstock]

Not super familiar with these handlers, but the flow makes sense. LGTM

[Hweinstock]

what exactly is this case for? What do we do differently when the tab is used/not used?

[jpinkney-aws]

It was a note from Oksana's original p.o.c: https://github.com/aws/language-servers/pull/733/files. As far as I understand in flare you can't create a tab and then later convert it. In the old version we were basing things on tab types which wouldn't exist in chat-client so instead we're just checking if someones interacted with the current tab before re-using it. If its used we create a new tab, otherwise we re-use the current tab