[AXON-1545] refactor rovodev analytics

[sdzh-atlassian]

What Is This Change?

Note: no change to behaviour or presentation - refactoring only

This PR is a somewhat broad rework of how analytics are implemented, scoped to rovodev-related stuff.

The main reasoning behind this is to avoid dragging the legacy implementation of analytics from into the new rovodev, whatever shape that takes :D

Change	Before	After
Explicit types for all relevant events
Finalize and send events in a single step
Options object across the board - no more magic with ordinal parameters
Single entrypoint for analytics	-/-	Telemetry, Performance, and Dwell events are defined in the same place and all sent through extensionApi.analytics

What's NOT in this PR?

• Actual automatic generation of the event types (doable, but will need to happen later)
• performanceEvent in src/analytics.ts still references rovodev but is now unused, it'll be cleaned up separately
• We still use trackEvent from src/analytics.ts to enrich the events with stuff like userId - that will need to be moved separately

How Has This Been Tested?

Somewhat extensively :D

• All tests that have been moved around kept their assertions, meaning there is literally no change to the shape of the events we actually send out
• Traced a bunch of event sends in debug
• [still going] Dumped all events we send to check if the (currently untested) single-event-per-prompt logic holds. Honestly, this is kind of tricky, so I might actually add tests for that in a separate PR

Basic checks:

• npm run lint
• npm run test

[sdzh-atlassian]

This file replaces rovodevAnalyticsTypes with a different approach to event definition, but same content otherwise

[sdzh-atlassian]

Moved to src/rovo-dev/rovoDevTelemetryProvider.test.ts without changes to the assertions

[sdzh-atlassian]

Deleted in favour of using explicit types and a discriminated union in analyticsApi.sendTrackEvent

[jwang19-atlassian]

I saw we have same func in analytics.ts file
just curious are these two same event?