feat(amazonq): display test plan summary and refactor shortAnswer to accommodate API changes

[chungjac]

Problem

• API has been refactored with new fields
• shortAnswer will eventually be deprecated
• new field jobSummary which has a summary about tests that were generated

Solution

• implemented new field: packageInfoList and its subfields
• display test summary in chat

Screen.Recording.2025-03-11.at.10.59.44.AM.mov

TODO:

• integrate new API fields: buildCommand (once build exec is released), packageSummary, fileSummary, etc
• remove all unused instances of shortAnswer

---

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

[laileni-aws]

Was this ShortAnswer being used any where in the project apart from build and execute in public master branch?

[chungjac]

Not being used anywhere else. I will eventually delete this after I do the shortAnswer refactoring for build exec

[laileni-aws]

LGTM.

Can you do E2E testing in these 3 scenarios?

• Success(both ACCEPTED/REJECTED)
• Failed
• Cancelled

[chungjac]

Completed testing for success, failed, and cancelled scenarios

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