fix(android): Bind the NDK crash service as important

Without `BIND_IMPORTANT`, a foreground app raises its bound crash
service process only to the visible oom adj (100), so lmkd would kill
the service before the app under memory pressure. The flag gives the
service the app's own adj (0) while the app is on top, without
lowering the app's priority the way `BIND_ABOVE_CLIENT` would.

Author: jpnurmi

sentry-android-ndk-outproc/src/main/java/io/sentry/android/ndk/SentryNdkCrashService.java

@@ -304,11 +304,13 @@ public void onBindingDied(final @NotNull ComponentName name) {
           }
         };
 
+    // a foreground app raises the service process only to visible without BIND_IMPORTANT
+    final int flags = Context.BIND_AUTO_CREATE | Context.BIND_IMPORTANT;
     if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.Q) {
       // deliver callbacks on the binder thread, the caller blocks on the latch
-      bound[0] = context.bindService(intent, Context.BIND_AUTO_CREATE, Runnable::run, connection);
+      bound[0] = context.bindService(intent, flags, Runnable::run, connection);
     } else {
-      bound[0] = context.bindService(intent, connection, Context.BIND_AUTO_CREATE);
+      bound[0] = context.bindService(intent, connection, flags);
     }
     if (!bound[0]) {
       return null;