feat: introduce telemetry

[f1ames]

This PR fixes #24.

Based on #31 and should be merged after it.

Changes

• Introduced Telemetry, see below for events list with properties.
• Added enableTelemetry config option (trueby default).
• Was inspired by Desktop, so we have install and session events based on similar logic as Desktop has.
• Used machineId provided by VSC env.
• Each event also sends native VSC sessionId. This can be used to group all events from single session (new session is when VSC instance is started/restarted).
• There is VSC native TelemetryLogger, but I realized a bit too late. Still I think what we have now is quite stable and good enough for now.

vscode-monokle/src/utils/telemetry.ts

Lines 69 to 97 in 02dc37e

	export type EventStatus = 'started' | 'success' | 'failure' | 'cancelled';
	export type BaseEvent = {status: EventStatus, error?: string};
	export type Event = keyof EventMap;
	export type EventMap = {
	'ext/installed': BaseEvent & {appVersion: string; deviceOS: NodeJS.Platform};
	'ext/session': BaseEvent & {appVersion: string, startTimeMs: number};
	'ext/session_end': BaseEvent & {endTimeMs: number, timeSpentSec: number};
	'command/login': BaseEvent & {method?: string};
	'command/logout': BaseEvent;
	'command/validate': BaseEvent & {rootCount?: number};
	'command/show_panel': BaseEvent;
	'command/show_configuration': BaseEvent & {configurationType?: string};
	'command/bootstrap_configuration': BaseEvent & {configurationType?: string};
	'command/synchronize': BaseEvent;
	'config/change': BaseEvent & {name: string; value: string};
	// When new folder is added/removed to/from VSC workspace.
	'workspace/change': BaseEvent & {rootCount: number};
	// When validation is completed for a workspace, usually triggered by file modification.
	'workspace/validate': BaseEvent & {
	resourceCount?: number,
	configurationType?: string,
	isValidConfiguration?: boolean,
	validationWarnings?: number,
	validationErrors?: number,
	};
	// When policy is synced from Monokle Cloud.
	'policy/synchronize': BaseEvent & {errorCode?: string};
	};

Fixes

• None.

Checklist

• tested locally
• added new dependencies
• updated the docs
• added a test

[devcatalin]

LGTM

[f1ames]

I rechecked if we can send telemetry events differently, so properties are split in MixPanel instead of being shown as single property, but it seems this is how @segment/analytics-node works and there is no easy way to change it.