OAT telemetry instrumentation

Summary of changes 🔍

Adding Telemetry to OAT actions. Added telemetry to be able to respond all these questions: High level usage Daily active users How many times does each user import and export in a day? How many models, relationships, inheritances and components are in each import / export? How many ontologies does each user have? How many models are in each ontology? How many models are v2 vs v3? How many relationships, inheritances and components are in each ontology?

Feature usage How often is DTDL manually edited and saved? How often is the path of a modal changed and saved? How often is the version of a model changed and saved? How often is a user searching for a model in the left panel? How often do users use the "auto layout" button? How often are properties added to a model and saved? Which property types are added? How often do imports fail? Is it due to reference limitation or syntax? If limitation: how many models, relationships, inheritances and components does it have?

And also some reducer actions tied to telemetry for extra insight into usage.

Testing 🧪

N/A

Checklist ✔️

[ ] Linked associated issue (if present)
[ ] Added relevant labels
[ ] Requested developer reviews
[ ] Request UI review from design / PM
[ ] Verify all code checks are passing

microsoft / iot-cardboard-js