fix(amazonq): filter out frequent client error from codegeneration telemetry

[linyuxi-0511]

Problem

We are mistakenly counting several client-side failures as service faults, which is affecting our availability metrics.

Solution

Exclude frequent client errors from faults, they should be errors.

there are multiple layers of errors, some of those are categorized to toolkit level errors, for example this part:

case MonthlyConversationLimitError.name:
case CodeIterationLimitError.name:
case PromptRefusalException.name:
case NoChangeRequiredException.name:

Others are defaulting to ToolkitError with messages.

Ideally we should add more error models to toolkit, but for now to make a quick fix, I just looked into the error msg, similar to what we do here:

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

Line 198 in 02d21a2

e.message.includes('limit for number of iterations on a code generation'))

---

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