fix(amazonq): Split trace server logs into separate output channel

[jpinkney-aws]

Problem

In the last few months we reduced the amount of output channels. This includes having the workspace context language server log to the "Amazon Q logs" output channel. However, the codewhisperer language server always creates the "Amazon Q Language Server" output channel

Solution

When the trace server is enabled ('amazonq.trace.server' in the vscode settings), output to a seperate channel because its extremely noisy, otherwise send the logs to the "Amazon Q Logs" output channel

---

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