fix: H.stop should stop otel exporters

[Vadman97]

Summary

Ensure that H.stop() shuts down OpenTelemetry exporters.

How did you test this change?

H.stop() now stops otel instrumentation; tested via e2e nextjs app

extensive testing of start-after-stop

Are there any deployment considerations?

no

---

Note

Ensure H.stop() and LDObserve.stop() fully shut down OTEL providers; switch metrics to getMeter() with guards and reset instrument caches; add test buttons and session replay config tweaks.

• SDK (client):
  • Use getMeter() for metrics (createGauge/Counter/Histogram/UpDownCounter) with null-guards in sdk/highlight-run/src/client/index.tsx.
  • After setupBrowserTracing, clear metric instrument caches to bind to the new meter.
  • On stopRecording, call shutdown() to stop OTEL providers.
• SDK (OTEL):
  • In sdk/highlight-run/src/client/otel/index.ts, prevent double-initialization if tracer or meter already exists.
  • Implement shutdown() to asynchronously shut down tracer and meter providers and unset them.
  • Expose getMeter(); remove direct metrics.getMeter(BROWSER_METER_NAME) usage.
• SDK (observe):
  • Mirror metric getMeter() usage and cache resets in sdk/highlight-run/src/sdk/observe.ts.
  • Replace manual provider shutdowns with centralized shutdown() in stop().
• E2E apps:
  • Add buttons to trigger H.recordMetric, H.start, H.stop in e2e/nextjs/.../highlight-buttons.tsx.
  • Extend session replay config (env, inline assets, canvas recording, sampling) in e2e/react-router/src/ldclientLazy.tsx.

^{Written by Cursor Bugbot for commit b092635. This will update automatically on new commits. Configure here.}