chore: update emit metric function to differentiate tests

[tejas2008]

Background

• The Codegen Canary workflow comprises three distinct test suites:
  1. build-app-ts
  2. build-app-android
  3. build-app-swift
• To improve error detection speed and efficiency, updates to the Canary frequency and alarms were necessary.
• Separating metrics for each test suite facilitates easier troubleshooting during ALARM states and helps have fewer data points to consider during each Evaluation period for the workflow.

Changes Implemented

1. Enhanced _emitCodegenCanaryMetric function:
   • Added a new test dimension to differentiate between test suites.
   • The test dimension now includes the following values:
     • ts for TypeScript tests
     • swift for Swift tests
     • android for Android tests
   • These values correspond directly to their respective TEST_SUITE in the canary_workflow.yml.

Testing

1. Deployed local changes to a personal CodeBuild Testing account.
2. Executed the Codegen canary workflow to validate:
   • Correct metric naming conventions
   • Proper functionality of the new dimension

Amazon Drive Link If image not visible

Checklist

• PR description included
• Relevant documentation is changed or added (and PR referenced)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[dzhan-aws]

Dummy curiosity question, do we know why the region is tight to us-west-2? Does that mean we only run codegen canary in this region?

[tejas2008]

The region us-west-2 just signifies the metrics will be visible in the us-west-2 region in AWS CloudWatch dashboard. It is not associated or related to canary running in this region, to be precise the codegen canary runs in us-east-1 and thus has no relation to the above region.