fix(android): register the ndk context ourselves — tao 0.35 stopped doing it

tao 0.34 registered it during startup; 0.35 dropped that and nothing else
in the tauri 2.11 stack does, so every ndk_context consumer (iroh's DNS
reader, cpal, netdev, our JNI fallbacks) panicked unconditionally — and a
panic escaping the app main is a process abort via tauri's stop_unwind.
MainActivity.onCreate now hands the activity to Rust, once per process,
restoring the 0.34 semantics; the service-only process stays unregistered
as before and keeps failing soft through the guards.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Author: JSKitty

src-tauri/gen/android/app/src/main/java/io/vectorapp/MainActivity.kt

@@ -28,6 +28,9 @@ class MainActivity : TauriActivity() {
 
         @JvmStatic
         external fun nativeOnResume()
+
+        @JvmStatic
+        external fun nativeRegisterNdkContext(activity: android.app.Activity)
         @JvmStatic
         external fun nativeOnPause()
         @JvmStatic
@@ -128,6 +131,11 @@ class MainActivity : TauriActivity() {
     override fun onCreate(savedInstanceState: Bundle?) {
         super.onCreate(savedInstanceState)
 
+        // Hand Rust the activity for ndk_context (tao 0.35 stopped registering it).
+        try { nativeRegisterNdkContext(this) } catch (e: Throwable) {
+            android.util.Log.e("MainActivity", "nativeRegisterNdkContext failed", e)
+        }
+
         // Ensure hardware acceleration is enabled
         window.addFlags(android.view.WindowManager.LayoutParams.FLAG_HARDWARE_ACCELERATED)