Send Event metrics via Telemetry

[Leo10Gama]

Which issue(s) does this change fix?

N/A

Why is this change necessary?

With this change, previously implemented Event tracker methods will be able to have their information sent via Telemetry. This provides us with a clear and concise way to actually look at the Event data.

How does it address the issue?

The previously added EventTracker class is imported into the Metric class, allowing access to the Events that are added to it by other methods. Since the decorator function is run after the primary SAM commands are run, it guarantees that any Event information is collected after all commands are executed.

What side effects does this change have?

With this new metric in place, the Metric class' metricSpecificAttributes field will have one additional value, "events". This will be a list, containing JSON objects with the following format:

{
  "event_name":  "SomeName",
  "event_value": "SomeValue"
}

Mandatory Checklist

PRs will only be reviewed after checklist is complete

• Add input/output type hints to new functions/methods
• Write design document if needed (Do I need to write a design document?)
• Write/update unit tests
• Write/update integration tests
• Write/update functional tests if needed
• make pr passes
• make update-reproducible-reqs if dependencies were changed
• Write documentation

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

[hawflau]

LGTM! Thanks for making the changes!