feat: core telemetry functionality

[blva]

• adds telemetry framework
• adds auth and unauth telemetry emission
• adds caching if events can't be published
• adds support to disable telemetry

next:

• add more events
• add unit tests
• check if we can add int tests

[blva]

note: this is a draft, will do some cleanup and change tests, looking for feedback on the code architecture

[coveralls]

Pull Request Test Coverage Report for Build 14622981460

Details

• 53 of 92 (57.61%) changed or added relevant lines in 8 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage decreased (-3.2%) to 75.182%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
src/telemetry/eventCache.ts	8	13	61.54%
src/common/atlas/apiClient.ts	3	15	20.0%
src/telemetry/telemetry.ts	16	38	42.11%

Totals
Change from base Build 14619684116:	-3.2%
Covered Lines:	624
Relevant Lines:	775

---

💛 - Coveralls

[gagik]

Great start 🚀

[gagik]

I'd move this to MACHINE_METADATA and maybe get rid of individual global constants

[blva]

We use it in the client though, so wanted to keep it here where is common

[gagik]

it's a bit confusing for me as it is inside a configuration, which to me means it is configurable

[fmenezes]

right now we use this as the toolname, we also have resources, I think this should contain "tool" | "resource" | "prompt" and another one maybe called tool_name

[blva]

yes, we should have a category property where we can set "tool" but the idea is to keep command for all based on the tracking plan

[fmenezes]

But how can you tell which is which?

[blva]

category: "tool"
command: "connect" | "list-projects" ...

[gagik]

Awesome work 🚀 one last note about Telemetry being initialized in every tool that may be worth addressing