feat(browser): Document unregisterOriginalCallbacks option in browserApiErrors integration page (#13859)

Documents a new option added via
getsentry/sentry-javascript#16412. Also added a
troubleshooting section as adding this option was the result of
investigating a user-reported SDK issue
(getsentry/sentry-javascript#16398)

Co-authored-by: Alex Krawiec <alex.krawiec@sentry.io>

Author: Lms24

docs/platforms/javascript/common/configuration/integrations/browserapierrors.mdx

@@ -40,6 +40,7 @@ Sentry.init({
       requestAnimationFrame: true,
       XMLHttpRequest: true,
       eventTarget: true,
+      unregisterOriginalCallbacks: true,
     }),
   ],
 });
@@ -110,3 +111,12 @@ List of default event targets:
 - `XMLHttpRequest`
 - `XMLHttpRequestEventTarget`
 - `XMLHttpRequestUpload`
+
+### `unregisterOriginalCallbacks`
+
+_Type: `boolean`_
+
+Unregister the original `EventTarget.addEventListener` callbacks.
+If you experience issues with this integration (or the SDK) causing double invocations of an `addEventListener` callback, set this option to `true`.
+This is usually a sign of the SDK being initialized too late in the lifecycle of the page.
+If this is the case, you might want to consider initializing the SDK as early as possible to avoid this issue.

docs/platforms/javascript/common/troubleshooting/index.mdx

@@ -389,6 +389,18 @@ Remember to pass in `true` as the second parameter to `addEventListener()`. With
 </Expandable>
 </PlatformCategorySection>
 
+<PlatformCategorySection supported={['browser']}>
+
+<Expandable permalink title="SDK causes double invocations of `addEventListener` (e.g. duplicated click events)">
+
+In very rare cases, the SDK can cause callbacks added via `addEventListener` to an event target (such as a button) to be invoked twice.
+This is usually a sign of the SDK being intialized too late in the lifecycle of the page. If you can, try initializing the SDK earlier in your application.
+
+If this is not possible or doesn't apply to your use case, set the `unregisterOriginalCallbacks` option in the [`browserApiErrors` integration](../configuration/integrations/browserapierrors) to `true`.
+
+</Expandable>
+</PlatformCategorySection>
+
 <Expandable permalink title="Build errors with vite">
 
 If you're using the [Vite Bundler](https://vitejs.dev/) and a Sentry NPM package, and you see the following error: