fix(android-ndk): Support byteProvider-based attachments in NdkScopeObserver

Previously, attachments created with a byteProvider (e.g., via
Attachment.fromByteProvider() or fromScreenshot()) were silently
skipped because both getPathname() and getBytes() return null for
these attachments. This caused data loss for native crash reports.

This fix adds support for byteProvider-based attachments by invoking
the callable on the background thread (via executor service) to
resolve the bytes before passing them to the native scope.

Author: cursoragent

sentry-android-ndk/src/main/java/io/sentry/android/ndk/NdkScopeObserver.java

@@ -170,6 +170,34 @@ public void addAttachment(final @NotNull Attachment attachment) {
       return;
     }
 
+    final java.util.concurrent.Callable<byte[]> byteProvider = attachment.getByteProvider();
+    if (byteProvider != null) {
+      final String filename = attachment.getFilename();
+      try {
+        options
+            .getExecutorService()
+            .submit(
+                () -> {
+                  try {
+                    final byte[] providedBytes = byteProvider.call();
+                    if (providedBytes != null) {
+                      nativeScope.addAttachmentBytes(providedBytes, filename);
+                    }
+                  } catch (Throwable e) {
+                    options
+                        .getLogger()
+                        .log(
+                            SentryLevel.ERROR,
+                            e,
+                            "Scope sync addAttachment failed to resolve byteProvider.");
+                  }
+                });
+      } catch (Throwable e) {
+        options.getLogger().log(SentryLevel.ERROR, e, "Scope sync addAttachment has an error.");
+      }
+      return;
+    }
+
     options
         .getLogger()
         .log(SentryLevel.DEBUG, "Scope sync addAttachment skips attachment without path or bytes.");