fix(search): use editingQuery instead of presentationFlow in startSea… (#2942)

fix(search): use editingQuery instead of presentationFlow in startSearch fixes #2914

presentationFlow is collected asynchronously from queryFlow. When a
history item is clicked, setQuery() and startSearch() run synchronously
on the main thread with no coroutine dispatch in between, so
presentationFlow.value is always stale at the time startSearch() reads
it. This causes startSearch to pass an empty string to
SearchPageState.startSearch(), which then overwrites queryFlow back to
empty and calls searchState.clear(), making results disappear.

editingQuery is a synchronous mutableStateOf written by setQuery(), so
it always reflects the correct value at call time.

Author: wellorbetter

app/shared/ui-exploration/src/commonMain/kotlin/ui/exploration/search/SuggestionSearchBarState.kt

@@ -104,7 +104,7 @@ class SuggestionSearchBarState(
     }
 
     fun startSearch() {
-        val rawQuery = presentationFlow.value.query
+        val rawQuery = editingQuery
         val query = rawQuery.trim()
         val tags = tagsProvider()
         if (query != rawQuery) {