test(frontend): cover Onramper open analytics

[cursor]

Motivation

Recent OnRamper changes added trackOnramperOpen to report success and failure outcomes for opening signed widget URLs. That payload is business-relevant telemetry: regressions could hide signing failures, rate limits, or selected-token attribution from dashboards.

Risky behavior now covered:

• Successful OnRamper open events include the selected token metadata and success status.
• Error OnRamper open events include severity, error type, error message, and omit token_address when no token address is available.

Changes

• Added focused trackOnramperOpen coverage in src/frontend/src/tests/lib/services/analytics.service.spec.ts.
• Covered both success and error payload shapes without changing production behavior.

Test files added/updated:

• src/frontend/src/tests/lib/services/analytics.service.spec.ts

Why these tests materially reduce regression risk:

• They pin the analytics contract used by the new OnRamper open flow, including optional token-address behavior and failure classification that downstream dashboards rely on.

Tests

• npm run test -- src/frontend/src/tests/lib/services/analytics.service.spec.ts
• npm run format
• npm run lint -- --max-warnings 0
• npm run check
• npm run test

Note: The first targeted test attempt failed before running because dependencies were not installed and .svelte-kit/tsconfig.json had not been generated. After installing locked dependencies with Node 24.11.0 and running npm run prepare, the targeted and full test runs passed.