fix: Add guard for phantom event

[HazAT]

No description provided.

[jan-auer]

So I have a theory about this. Here, we call the generic captureEvent:

sentry-electron/src/main/backend.ts

Lines 149 to 150 in f4776e7

	// @ts-ignore __INTERNAL_MINIDUMP is not assignable to event
	captureEvent({ __INTERNAL_MINIDUMP: true });

This is a scope listener on a hub, so I would expect that it always routes to the right backend, but what if a different client is bound? Particularly, it says crashed_process: browser in those events, so potentially this is being routed through the wrong client?

I was wondering if we should just be calling the backend's sendEvent directly rather than the generic captureEvent there.

[HazAT]

It has to go through captureEvent to have all the context for the event. I am going to ship this and lets see.