feat(amazonq): get logs generated by the Agent

[karanA-aws]

Problem

Users currently cannot access logs generated by the Agent when it executes user commands during code generation.

Solution

The output generated by the Agent during user command execution will be captured and written to the user's logs. This ensures that:

• Command execution logs are persisted locally
• Users can access the logs directly from their repository for troubleshooting.

---

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

[justinmk3]

what is the typical value of logFileInfo.fileContent ? is it potentially all of the contents of a big text file, or is it guaranteed to be just a small bit of text (e.g a filename or something like that)?

full text files should not be printed to the logs.

consider using truncate() to avoid printing excessively long text.

aws-toolkit-vscode/packages/core/src/shared/utilities/textUtilities.ts

Line 21 in 708f538

export function truncate(s: string, n: number, suffix?: string): string {

[karanA-aws]

The intent of the feature is to display the logs of the commands executed by the Agent to the User. Therefore the length of the logFileInfo.fileContent can be large which will be reflective of the logs generated if the user would've ran the code in their execution environment.

[justinmk3]

Then it should be truncated to avoid edge cases where the logs are very large. Writing MB or GB to the log file isn't ever going to be useful to anyone, and is likely to cause problems instead.

Please always consider edge-cases when writing code.

[karanA-aws]

Truncating to limit the content length in revision.