fix bugs that doesnt count develop and review and cli used count.

[tkitayat912]

Problem

Disabled features (Development, Review, CLI)

1. Review function
   There are tests in packages/amazonq/test/e2e/amazonq/review.test.ts, but I can't find the telemetry transmission code
   There is a lack of implementation that sends execution results of the /review command to the dashboard

2. Development features
   No specific “development” telemetry event is defined
   There is a lack of dedicated telemetry to track development-related activities

3. CLI functionality
   Can't find SAM CLI related telemetry
   There is a CLI implementation in packages/core/src/shared/sam/cli/, but the mechanism to send usage status to the dashboard is insufficient
   solutions

To be reflected in the dashboard, the following additional telemetry events must be implemented:
Review features: /review command execution, results, scan completion event
Development features: code generation, project creation, development activity tracking
CLI features: SAM CLI execution, deployment, and build command usage
The current Chat and Inline Code are tracked in detail with dedicated telemetry helpers, so they are correctly reflected on the dashboard.

Solution

I've implemented the following additional telemetry events:
Review function
AmazonQ_ReviewStart - Review Begins
AmazonQ_reviewComplete - Review completed (including number of questions)
AmazonQ_ReviewError - review error
AmazonQ_reviewFixApplied - fix applied
Development features
AmazonQ_codeGeneration - code generation
AmazonQ_ProjectCreation - Project Creation
AmazonQ_developmentActivity - development activity
amazonQ_featureUsage - feature usage
CLI functionality
amazonq_samcommand - execute SAM command
AmazonQ_saminit - SAM Initialization
AmazonQ_samdeploy - SAM deployment
AmazonQ_samLocalInvoke - SAM Local Execution
These telemetry events will allow the dashboard to reflect the results of Development, Review, and CLI runs. Detailed metrics such as usage, success rate, and execution time for each feature are collected and visualized in the Activity Dashboard.

---

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