fix(amazonq): downloadExportResultAcrchive api not passed with profileArn and cause 400 error

[Will-ShaoHua]

Problem

The CreateUploadUrl and StartTestGenerationJob requests succeeded with the profile ARN attached. However, the ExportResultArchive requests were made without this profile ARN, leading to inconsistent profile resolution between operations.

Solution

---

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

[justinmk3]

changelog ?

[Will-ShaoHua]

changelog ?

oh i forgot to push

[Will-ShaoHua]

fyi @justinmk3 this pr is not ready yet

[Will-ShaoHua]

i am querying service logs to find out what else we missed

[neilk-aws]

Should this also be changed for the FeatureDev client implementation?

aws-toolkit-vscode/packages/core/src/amazonqFeatureDev/client/featureDev.ts

Line 246 in dd14b98

public async exportResultArchive(conversationId: string) {

[Will-ShaoHua]

Should this also be changed for the FeatureDev client implementation?

yes

[Will-ShaoHua]

@neilk-aws as your request, funtionally tested / dev

[Will-ShaoHua]

/ test

[Will-ShaoHua]

/ review

[Will-ShaoHua]

thank you all