chore(repo): Updated CW Metrics

[fjnoyp]

Issue #, if available:

Description of changes:

Build upon existing CW Metric reporting to track additional dimensions in each metric.

Refactor CW Metric reporting to use Github Actions Dart -> JS framework.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[fjnoyp]

Wrapper for log_cw_metric

Auto fills:
repo: ${{ github.repository }}
run-id: ${{ github.run_id }}

And calls configure AWS credentials

So that workflows that need to log metrics don't need to worry about these extra details.

[fjnoyp]

github does not return the current job id. While you can get current run id, when requesting run information you get all the jobs for that run. Thus to differentiate an individual job of that run, I needed to have this parameter for finding the particular job.

[dnys1]

Most of this info can be pulled from the action's context instead of needing to be passed in manually.

[fjnoyp]

Thanks using the github context helped.

Still needed to keep some:

1. Job status is only in the job.context.jobStatus
2. Switched jobIdentifier (hardcoded in our workflow calls) with dart parsing logic on a matrix input

This extra complexity is largely due to Github not providing the current job id, which means we can only get the entire job list of a workflow run. We need some form of identifier to know which of those jobs is the actual job id we are currently running in.

[dnys1]

You're already going through the hassle of passing in this value, why not pass in the category itself and compute it ahead of time as part of the generate workflows command?

[fjnoyp]

That makes sense, though I'd rather keep our github action workflows clean and avoid adding additional params that are only needed for my logging flows.

Alternatively we can directly accept a packageName to the log metric method instead.

[dnys1]

I've opened #3767 to make working with the GitHub context easier.