Plan to support Telemetry Collection for Emitter in TypeSpec VS Code Extension

[lirenhe]

Clear and concise description of the problem

Description:

We need to support telemetry collection from our emitters in the TypeSpec VS Code extension. It would include error when emitting fails, some of the options when emitter is triggered, etc.
The goal is to gather useful data to improve our CodeGen while ensuring compliance with privacy regulations such as GDPR.

Today, typespec extension could get all the logs that our emitters output, then we need to decide what information is useful for collection. This work is related to #5298

I don't think typespec extension would collect output for all emitters, a white list of emitter should be fine.

A couple of requirements for Telemetry collection

• We would only log the success/failure of client/server emitters without other detailed information.
• We need user identity to get a brief understanding of the behavior. e.g. How many times does a user invoke the client emitters, How often do they invoke a specific emitter.

cc @lmazuel

Checklist

• Follow our Code of Conduct
• Read the docs.
• Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

[lirenhe]

@chunyu3, we also need the option to allow user to turn off the telemetry collection.

[RodgeFu]

@chunyu3, we also need the option to allow user to turn off the telemetry collection.

vscode will help to handle it when we adopt its library which will be done in #5298 . thx.