feat: Renderer process ANR detection with stack traces

[timfish]

When getsentry/sentry-javascript#9191 is merged, anr-utils.ts in this PR can be removed.

This PR adds ANR detection for the Electron renderer processes.

This is entirely configured from each renderer processes:

import { init } fron '@sentry/electron/renderer';

init({
  dsn: '__DSN__',
  anrDetection: { pollInterval: 200, anrThreshold: 2000, captureStackTrace: true },
})

Renderer ANR has no overhead unless a renderer starts sending ANR status updates to the main process.

[AbhiPrasad]

I'm in favor of turning it on by default 👍

[timfish]

This PR is still waiting on a few upstream bits to be released but it's now configured entirely from the renderer process.

import { init } fron '@sentry/electron/renderer';

init({
  dsn: '__DSN__',
  anrDetection: { pollInterval: 200, anrThreshold: 2000, captureStackTrace: true },
})

It also now enables renderer ANR by default but without stack traces enabled since this will add overhead.

Since renderer ANR is no longer configured form the main process, we should probably change how the main process ANR is configured since this was chosen to leave config points for the renderer.

Current:

await enableAnrDetection({ mainProcess: { captureStackTrace: true }});
runApp();

I think this should probably highlight its for the main process only:

await enableMainProcessAnrDetection({ captureStackTrace: true });
runApp();

[AbhiPrasad]

anr utils changes released with https://github.com/getsentry/sentry-javascript/releases/tag/7.74.0

[timfish]

Done, @AbhiPrasad what do you think about the above mentioned renaming of enableAnrDetection to enableMainProcessAnrDetection and removing the mainProcess config option?

[AbhiPrasad]

Yeah I think let's use enableMainProcessAnrDetection here, makes it behavior very clear.