fix(amazonq): Skip including deleted files for FeatureDev context.

[neilk-aws]

Problem

When zipping context for /dev, customer build processes (file watchers, etc.) may delete build artifacts we’ve already enumerated but have not added to the archive. As a best practice, customers should .gitignore these types of files, but in the event they don't, this has the potential to block /dev from running.

Solution

Skip affected files, which are not found when adding to zip context for Feature Dev.

---

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

[Hweinstock]

Is there a way we can test this behavior? Something along the lines of having collectFiles return some files that don't exist when we try to access them?

[justinmk3]

does it set a code ? try hasCode

aws-toolkit-vscode/packages/core/src/shared/errors.ts

Line 602 in 3d90772

function hasCode<T>(error: T): error is T & { code: string } {

[neilk-aws]

This error does not set a code: https://github.com/cthackers/adm-zip/blob/1cd32f7e0ad3c540142a76609bb538a5cda2292f/util/errors.js#L56

[neilk-aws]

Is there a way we can test this behavior? Something along the lines of having collectFiles return some files that don't exist when we try to access them?

This is mitigating a situation where there is a race condition and the file is deleted as they are being zipped. In this case, collectFiles would not report any files do not exist, and we would only discover it when they are being looked up.