rewrite plugin-contextualize without domain

[djskinner]

Goal

• rewrite plugin-contextualize to not use the deprecated node domain API
• use a similar approach and the same AsyncLocalStorage instance as in replace node domain API with AsyncLocalStorage #1898

Changeset

• rewrite plugin-contextualize to not use the deprecated node domain API.
  • The usage API remains the same (contextualize: (fn: () => void, onError: OnErrorCallback) => void) but there are changes in behaviour.
  • Before, the plugin would capture unhandled errors regardless of the config values autoDetectErrors and enabledErrorTypes.unhandledExceptions. Now, the plugin will only capture unhandled exceptions if both autoDetectErrors and enabledErrorTypes.unhandledExceptions are enabled.
  • Before, the plugin was unable to add context to unhandled promise rejections. Now, (since node 16) unhandled promise rejections are captured with context if autoDetectErrors and enabledErrorTypes.unhandledRejections are enabled.

Testing

• e2e coverage covering both uncaught exceptions and unhandled rejections
• no unit test coverage - it appears impossible to cover this in a meaningful way with jest

[github-actions]

@bugsnag/browser bundle size diff

	Minified	Minfied + Gzipped
Before	44.63 kB	13.64 kB
After	44.63 kB	13.64 kB
±	No change	No change

code coverage diff

<temporarily disabled>

Generated by 🚫 dangerJS against a18b793

[djskinner]

The change here is that the line " at process.EventEmitter.emit (domain.js:483:12)" is no longer present. This frame was being added due to the mere presence of require('domain') in the contextualize plugin, which is part of the node notifier and therefore also instantiated in aws lambda.