Open the sign-in URL through an ACTION_VIEW Intent on Android

The previous commit made the missing launcher honest; this gives Android a real
one, so Login Flow v2 can complete on device.

Builds `new Intent(ACTION_VIEW, Uri.parse(url))` and hands it to
`startActivity` over JNI. The JavaVM and Activity come from ndk_context, which
android-activity's glue populates at startup — the same handle Slint's backend
uses, so there is no second VM to reconcile.

The login worker is a plain std::thread and therefore unknown to the JVM, where
any JNI call would abort the process. jni 0.22 scopes attachment to a closure
rather than returning a guard, so the whole Intent is built and dispatched
inside `attach_current_thread` and the thread detaches on the way out.

Names use `jni_str!` and signatures `jni_sig!`, both compile-time: a typo is a
build error rather than a NoSuchMethodError on the device. A pending Java
exception is checked and cleared before returning, since leaving one pending
makes the next JNI call fail somewhere unrelated; in practice it means
ActivityNotFoundException, i.e. no browser installed.

jni is pinned to 0.22 to match Slint's Android backend.

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

ui/dr-ui/Cargo.toml

@@ -45,6 +45,12 @@ slint = { workspace = true, features = ["backend-winit"] }
 
 [target.'cfg(target_os = "android")'.dependencies]
 slint = { workspace = true, features = ["backend-android-activity-06"] }
+# Opening the sign-in URL needs an ACTION_VIEW Intent — Android has no
+# xdg-open. Version-matched to Slint's Android backend so both halves of the
+# process agree on the JavaVM types; ndk-context supplies the VM and activity
+# that android-activity's glue already stashed.
+jni = "0.22"
+ndk-context = "0.1"
 
 [build-dependencies]
 slint-build.workspace = true