feat: measure client activation at launch

[0xcadams]

What

Measure the CLI launch path from a developer starting init, login, dev, or publish to finishing setup or reaching a ready public URL. This provides the client side of the first-party activation funnel collected by tnl.dev.

Why

Existing command events count routine version checks, including disposable CI containers, and begin too late to see project configuration errors. A ready run alone cannot show where a new developer got stuck.

Changes

• Emit start, setup completion, and bounded pre-ready failure events with a fresh invocation ID, stable diagnostic codes, and existing opt-out behavior.
• Report ready publish runs once per invocation and avoid counting errors after readiness as activation failures.
• Stop reporting version checks and disable telemetry in the CI container smoke check.