Adding instrumentation to Azure toolsets to gather intelligence

### Clear and concise description of the problem

To support insights into internal service adoption and usage, we need to collect stats on active users. We do collect user information via VS Extension instrumentation. However, there seems to be anomalies in the user data collected. It would be reliable to directly collect from the TypeSpec toolset.

With that ask, TypeSpec Compiler with broader community usage would not be suitable to instrument. However for Azure toolset (autorest emitter, Azure.Core, ARM library), they can be instrumented to collect primarily internal user. The following is list of task breakdowns.

Tasks:
- [ ] Privacy Review
- [ ] New 1DS appID onboarding
- [ ] Determine initial data set and source (emitter vs library)
- [ ] Adding instrumentation

### Checklist

- [X] Follow our [Code of Conduct](https://github.com/azure/typespec-azure/blob/main/CODE_OF_CONDUCT.md)
- [X] Check that this issue is about the Azure libraries for typespec. For feature request in the typespec language or core libraries file it in the [TypeSpec repo](https://github.com/Microsoft/TypeSpec/issues/new/choose)
- [X] Read the [docs](https://azure.github.io/typespec-azure/).
- [X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.