Implement telemetry

[Dawe000]

Adds optional telemetry to the SDK: when apiKey (and optionally telemetryEndpoint) is set, read-only methods emit events to the ingest endpoint (fire-and-forget). No apiKey ⇒ no telemetry.

Changes

• New: src/core/telemetry.ts — TelemetryClient, categorizeError, default endpoint.
• SDK: apiKey and telemetryEndpoint in config; events for searchAgents, getAgent, loadAgent, searchFeedback, getReputationSummary (and Agent lifecycle where applicable).
• Tests: tests/telemetry-sdk.test.ts — tests with apiKey (including DB checks when Supabase env is set) and one test without apiKey.
• Config: tests/config.ts and .env.example include AGENT0_API_KEY, AGENT0_TELEMETRY_ENDPOINT, SUPABASE_URL, SUPABASE_SERVICE_ROLE_KEY.
• DevDep: @supabase/supabase-js for the DB assertion test only.

How to test

1. Without Supabase (API key only): Set AGENT0_API_KEY in .env, run npm test -- telemetry-sdk. All tests except “telemetry events are written to the database” run; that one is skipped.
2. With Supabase (full integration): In agent0-dashboard run supabase start, apply seed-telemetry-test-user.sql, run npx supabase functions serve. In agent0-ts set AGENT0_TELEMETRY_ENDPOINT, SUPABASE_URL, SUPABASE_SERVICE_ROLE_KEY in .env, then npm test -- telemetry-sdk. All tests run, including DB checks.