fix: suppress SIGABRT and EXC_BAD_ACCESS during Cocoa SDK init

Author: jpnurmi

src/Sentry/Platforms/Cocoa/SentrySdk.cs

@@ -200,11 +200,6 @@ private static CocoaSdk.SentryHttpStatusCodeRange[] GetFailedRequestStatusCodes(
     /// </summary>
     internal static CocoaSdk.SentryEvent? ProcessOnBeforeSend(SentryOptions options, CocoaSdk.SentryEvent evt, IHub hub)
     {
-        if (hub is DisabledHub)
-        {
-            return evt;
-        }
-
         // When we have an unhandled managed exception, we send that to Sentry twice - once managed and once native.
         // The managed exception is what a .NET developer would expect, and it is sent by the Sentry.NET SDK
         // But we also get a native SIGABRT since it crashed the application, which is sent by the Sentry Cocoa SDK.
@@ -239,6 +234,11 @@ private static CocoaSdk.SentryHttpStatusCodeRange[] GetFailedRequestStatusCodes(
             }
         }
 
+        if (hub is DisabledHub)
+        {
+            return evt;
+        }
+
         // We run our SIGABRT checks first before running managed processors.
         // Because we delegate to user code, we need to catch/log exceptions.
         try