fix(settings): initialise the default-installer flow before init reads it

Opening Settings on an emulator killed the process:

  FATAL EXCEPTION: DefaultDispatcher-worker-1
  java.lang.NullPointerException: Attempt to invoke interface method
    'void kotlinx.coroutines.flow.MutableStateFlow.setValue(java.lang.Object)'
    on a null object reference
      at SettingViewModel$updateDefaultInstallerStatus$1.invokeSuspend(SettingViewModel.kt:927)

_isDefaultInstaller was declared 480 lines below the init block that starts
the coroutine assigning it. Property initialisers run in declaration order,
so until the constructor reached line 850 the field was genuinely null, and
whichever of the two got there first decided whether the app lived.

Physical devices hid it: resolveActivity is an IPC, slow enough that the
constructor always finished first. An emulator answers fast enough to lose
the race — which is why this only ever showed up there.

Moved next to _shizukuState and _rootState, the other state init touches, with
a note about the ordering so it does not drift back down.

Swept the rest of the app for the same shape: one other flow is declared after
its init block (_selectedLanguage), but init never reaches it.

Verified on the emulator: Settings opens, process survives, zero uncaught
exceptions in logcat.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Author: nqmgaming

app/src/main/java/app/pwhs/universalinstaller/presentation/setting/SettingViewModel.kt

@@ -333,6 +333,18 @@ class SettingViewModel(
         if (backendFactory.rootSupportCompiledIn) RootState.UNKNOWN else RootState.UNAVAILABLE,
     )
 
+    /**
+     * Kept up here, with the rest of the state [init] touches, because it has to exist before the
+     * constructor reaches that block.
+     *
+     * It used to be declared 480 lines below, and `updateDefaultInstallerStatus()` — launched from
+     * init — assigned it from a coroutine. Property initializers run in declaration order, so the
+     * flow was still null whenever that coroutine won the race, and the process died with an NPE
+     * on a background thread. Physical devices hid it: resolveActivity's IPC took long enough for
+     * the constructor to finish first. An emulator returns fast enough to lose the race.
+     */
+    private val _isDefaultInstaller = MutableStateFlow(false)
+
     private val binderReceivedListener = Shizuku.OnBinderReceivedListener {
         Timber.d("Shizuku binder received")
         updateShizukuState()
@@ -847,8 +859,6 @@ class SettingViewModel(
         }
     }
 
-    private val _isDefaultInstaller = MutableStateFlow(false)
-
     /**
      * Toggles Universal Installer's DialogInstallActivity as the preferred handler for APK
      * install intents — the same mechanism Android uses when the user taps "Always" in the