(2) ref(tracing): Extract NativeFrames as standalone integration

[krystofwoldrich]

📢 Type of change

• Refactoring

📜 Description

This PR extracts Native Frames Tracking to a standalone integration. This is possible via client event spanStart and spanEnd which is available in JS v8. Before ReactNativeTracing integration ensured the Stall Tracking is started and stopped on transaction start and stop.

Moving the tracking to a standalone integration will let us measure usage of this feature (enabled integrations telemetry).

This PR introduces user facing breaking change.

Before

import Sentry from '@sentry/react-native';
Sentry.init({
  tracesSampleRate: 1.0,
  integrations: [
    new Sentry.ReactNativeTracing({
      enableNativeFramesTracking: true, // default true
    }),
  ],
});

After

import Sentry from '@sentry/react-native';
Sentry.init({
  tracesSampleRate: 1.0,
  enableNativeFramesTracking: true, // default true
});

💚 How did you test it?

sample app, tests

📝 Checklist

• I reviewed submitted code
• I added tests to verify changes
• No new PII added or SDK only sends newly added PII if sendDefaultPII is enabled
• All tests passing
• No breaking changes

Predecessor to this PR

• (1) ref(tracing): extract app start to a standalone integration #3852

[github-actions]

iOS (legacy) Performance metrics 🚀

	Plain	With Sentry	Diff
Startup time	1230.83 ms	1238.80 ms	7.96 ms
Size	2.36 MiB	3.06 MiB	714.24 KiB

[lucas-zimerman]

LGTM!

[github-actions]

iOS (new) Performance metrics 🚀

	Plain	With Sentry	Diff
Startup time	1239.96 ms	1243.57 ms	3.61 ms
Size	2.92 MiB	3.62 MiB	720.12 KiB

[github-actions]

Android (legacy) Performance metrics 🚀

	Plain	With Sentry	Diff
Startup time	433.73 ms	457.73 ms	24.00 ms
Size	17.73 MiB	20.04 MiB	2.31 MiB