fix(native/breakpad): capture abort() on Windows

[jpnurmi]

The handler was directly copied from inproc (#1446):

sentry-native/src/backends/sentry_backend_inproc.c

Lines 593 to 629 in 104513c

	static void
	handle_sigabrt(int signum)
	{
	(void)signum;
	// Capture the current CPU context
	CONTEXT context;
	RtlCaptureContext(&context);
	// Create a synthetic exception record for abort
	EXCEPTION_RECORD record;
	memset(&record, 0, sizeof(record));
	record.ExceptionCode = STATUS_FATAL_APP_EXIT;
	record.ExceptionFlags = EXCEPTION_NONCONTINUABLE;
	# if defined(_M_AMD64)
	record.ExceptionAddress = (PVOID)context.Rip;
	# elif defined(_M_IX86)
	record.ExceptionAddress = (PVOID)context.Eip;
	# elif defined(_M_ARM64)
	record.ExceptionAddress = (PVOID)context.Pc;
	# endif
	EXCEPTION_POINTERS exception_pointers;
	exception_pointers.ContextRecord = &context;
	exception_pointers.ExceptionRecord = &record;
	handle_exception(&exception_pointers);
	// If we get here, call the previous handler or terminate
	if (g_previous_sigabrt_handler && g_previous_sigabrt_handler != SIG_DFL
	&& g_previous_sigabrt_handler != SIG_IGN) {
	g_previous_sigabrt_handler(signum);
	}
	// Terminate the process - abort() must not return
	TerminateProcess(GetCurrentProcess(), 3);
	}

Example event: https://sentry-sdks.sentry.io/issues/7467638795

Close: #591

[jpnurmi]

A) Do we care to share the handler code somewhere?
B) Is it a feature, or rather a fix? 😅

[supervacuus]

A) Do we care to share the handler code somewhere?

I don't think this is a high-value module for reuse or downstream maintenance. Maybe one could even argue that keeping implementations separate allows the backends to add backend-specific context that should be distinct with the underlying UEF implementation.

B) Is it a feature, or rather a fix? 😅

I would call it a fix, but I don't think it matters much.

[jpnurmi]

I don't think this is a high-value module for reuse or downstream maintenance. Maybe one could even argue that keeping implementations separate allows the backends to add backend-specific context that should be distinct with the underlying UEF implementation.

I ended up with a shared helper after all, because including <signal.h> conflicts with breakpad's definitions:
https://github.com/getsentry/breakpad/blob/47d70322c848012ed801e36841767d7ffb79412d/src/google_breakpad/common/minidump_exception_linux.h#L52