fix(amazonq): should emit UTDE telemetry before applying the Edits content

[atonaamz]

Problem

For Edits, we emit UTDE telemetry after applying the Edits contents.
After we apply the Edits content, auto trigger may be performed. During the auto trigger, the session is closed and new session is created.
As a result, the session may be closed before we emit UTDE telemetry, resulting in no UTDE telemetry being emitted: https://github.com/aws/language-servers/blob/main/server/aws-lsp-codewhisperer/src/language-server/inline-completion/codeWhispererServer.ts#L616

For inline completion, we emit UTDE metrics before applying the new content: https://github.com/aws/aws-toolkit-vscode/blob/master/packages/amazonq/src/app/inline/completion.ts#L143-L159

Solution

Emit UTDE telemetry before applying the Edits content

---

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

[amazon-inspector-ohio]

⏳ I'm reviewing this pull request for security vulnerabilities and code quality issues. I'll provide an update when I'm done

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

[amazon-inspector-ohio]

✅ I finished the code review, and didn't find any security or code quality issues.