Refactor: Move survey navigation DB query to background thread

Moves the blocking Realm query in `DashboardActivity.handleSurveyNavigation` to a background thread to prevent potential ANRs.

- Converted `handleSurveyNavigation` to a `suspend` function.
- Wrapped the Realm query in `withContext(Dispatchers.IO)`.
- Used `realm.copyFromRealm` to pass the result to the main thread safely.
- Updated the call site in `handleNotificationIntent` to launch the function in `lifecycleScope`.

Author: google-labs-jules[bot]

app/src/main/java/org/ole/planet/myplanet/ui/dashboard/DashboardActivity.kt

@@ -387,7 +387,9 @@ class DashboardActivity : DashboardElementActivity(), OnHomeItemClickListener, N
 
             when (notificationType) {
                 NotificationUtils.TYPE_SURVEY -> {
-                    handleSurveyNavigation(relatedId)
+                    lifecycleScope.launch {
+                        handleSurveyNavigation(relatedId)
+                    }
                 }
                 NotificationUtils.TYPE_TASK -> {
                     lifecycleScope.launch {
@@ -411,10 +413,16 @@ class DashboardActivity : DashboardElementActivity(), OnHomeItemClickListener, N
         }
     }
 
-    private fun handleSurveyNavigation(surveyId: String?) {
+    private suspend fun handleSurveyNavigation(surveyId: String?) {
         if (surveyId != null) {
-            val currentStepExam = mRealm.where(RealmStepExam::class.java).equalTo("name", surveyId)
-                .findFirst()
+            val currentStepExam = withContext(Dispatchers.IO) {
+                Realm.getDefaultInstance().use { realm ->
+                    realm.where(RealmStepExam::class.java).equalTo("name", surveyId)
+                        .findFirst()?.let {
+                            realm.copyFromRealm(it)
+                        }
+                }
+            }
             AdapterMySubmission.openSurvey(this, currentStepExam?.id, false, false, "")
         }
     }