feat(amazonq): Customer pricing details for Amazon Q

[laileni-aws]

Customer Pricing Details for Amazon Q

Description

This PR adds customer pricing details for Amazon Q to improve transparency and user experience. The implementation provides clear pricing information for Amazon Q services within the VS Code extension.

Changes

• Added pricing details UI components
• Integrated pricing information with existing Amazon Q functionality
• Ensured pricing details are accurate and up-to-date

Technical Implementation:

• VSC sends Capability awsClientCapabilities.q.subscriptionDetails : true in initialization request.
• Server returns ServerCapability awsServerCapabilities.chatOptions.subscriptionDetails in initialization response:
  • set to false if subscriptionDetails is not in the request
  • set to true if subscriptionDetails is true in the request
  • set to false otherwise
• If user clicks on Account Details, VSC sends aws/chat/subscription/show event to language servers.
• Language server fetch required information from the backend and sends aws/chat/subscription/details to VSC which is sent to Flare ChatUI(Mynah-UI).

VSC-CX.Pricing.mov

Testing

• Verified pricing details display correctly in the extension
• Confirmed pricing information matches the official Amazon Q pricing
• Tested with both IAM and BuilderId logins.

Todo

• Add changeLog before release.
• This PR includes the Upgrade functionality framework, which is pending implementation in Language server. While currently inactive, this addition is forward-compatible and will seamlessly integrate once Flare implements the Upgrade feature.
• Once Language server completes the implementation, verify the Upgrade button functionality in the Account Details tab.

---

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