Wire activation-funnel analytics events

[udil-cloudinary]

Phase 1 POC, PR #2 of 2 — wires the activation-funnel events on top of the analytics infrastructure from #1187. See the POC definition and implementation plan.

Approach

Server-side events emit directly through the Analytics component; client-side wizard events go through the JS track() bridge → the internal /events REST route (which enriches them with the server-side param envelope).

Server-side

• plugin_activated (step 1) — install-type detection in Analytics::stash_activation() (called from Utils::install): fresh_install / reactivation / upgrade / downgrade, derived from the db_version install marker + version_compare. Stashed in a transient and emitted on the next admin load (so full mandatory params + session_id are present), then cleared. A new register_deactivation_hook persists _cloudinary_last_active so days_since_last_active can be computed on reactivation. Params: activation_type, previous_version, new_version, days_since_last_active.
• connection_test_result (3d) — in rest_test_connection (status, error_type, attempt_number).
• wizard_setup_submitted (5) — in rest_save_wizard (media_library, non_media, advanced, status).
• first_sync_started (8, one-time) — in Push_Sync::process_assets (asset_count).
• first_api_consumption (9, one-time) — via the existing cloudinary_uploaded_asset action; emitted on the first successful upload, then suppressed (api_endpoint, asset_type).

Client-side (wizard.js): wizard_started, wizard_signup_clicked, wizard_connect_viewed, credentials_entry_started, credentials_format_validated, connection_test_started, wizard_settings_viewed, wizard_setting_toggled, wizard_completed, wizard_dashboard_clicked.

Notes:

• One-time markers (first_sync_started, first_api_consumption) are guarded by wp_option flags.
• connection_test_result is server-side (richer error info); the client forwards attempt_number on the test request so the server event carries it.
• track() is now lazy-init so call-sites are order-independent. Still fail-silent end-to-end; nothing emits in production until cloudinary_analytics_enabled is on (default true) and an event fires.

QA notes

1. Fresh install: activate on a clean site → on the next admin page, plugin_activated with activation_type=fresh_install, previous_version absent.
2. Reactivation: deactivate, wait, reactivate → activation_type=reactivation with days_since_last_active. Bump/lower .version to exercise upgrade/downgrade.
3. Wizard: walk the setup wizard and confirm the client events fire in order (Network tab → cloudinary/v1/events), connection_test_result carries attempt_number, wizard_setup_submitted fires on save.
4. First use: run a sync → first_sync_started once; first successful upload → first_api_consumption once (re-syncing does not re-fire either).
5. Fail-safe: block the collector host → wp-admin stays fully usable; no console errors, no PHP fatals.
6. npm run lint:js, npm run lint:php, npm run build all pass.

Test matrix: WP 5.6 / 6.9.x / 7.0, PHP 7.4 / 8.x, single + multisite, classic + block.