Refactor(Settings): Remove redundant theme logic in SettingsFragment

The `SettingsFragment` has been updated to simplify the theme-switching logic. Previously, it contained code to determine the dark mode status and manually apply the theme.

This logic is now handled elsewhere, so the redundant `isDark` variable, the `when` statement, and the calls to `setThemeMode` and `reloadLauncher` have been removed. The fragment now only calls `resetThemeColors` when the theme preference is changed, streamlining the settings update process.

Author: CreativeCodeCat

app/src/main/java/com/github/codeworkscreativehub/mlauncher/ui/SettingsFragment.kt

@@ -353,8 +353,6 @@ class SettingsFragment : BaseFragment() {
         var toggledLockOrientation by remember { mutableStateOf(prefs.lockOrientation) }
         var toggledHapticFeedback by remember { mutableStateOf(prefs.hapticFeedback) }
 
-
-
         Column(
             modifier = Modifier
                 .fillMaxSize()
@@ -551,14 +549,7 @@ class SettingsFragment : BaseFragment() {
                                         val newTheme = themeEntries[newThemeIndex]
                                         selectedTheme = newTheme
                                         prefs.appTheme = newTheme
-
-                                        val isDark = when (newTheme) {
-                                            Constants.Theme.Light -> false
-                                            Constants.Theme.Dark -> true
-                                            Constants.Theme.System -> isSystemInDarkMode(requireContext())
-                                        }
-                                        setThemeMode(requireContext(), isDark, binding.settingsView)
-                                        reloadLauncher()
+                                        resetThemeColors()
                                     }
                                 }
                             )