fix: prevent skipped update in StateFlow

- use collected emission `it` instead of `StateFlow.value` so lastValue tracks only what was actually processed

When performing manual deduplication inside a collect block, reading StateFlow.value instead of the emitted value (it) allows the tracking variable to "race ahead" of the collector. If multiple updates occur rapidly (e.g., while the UI is in the background), the tracking variable may be updated to the latest value while processing an intermediate emission. This causes the collector to incorrectly drop the subsequent final emission as a duplicate.

Author: HS0204

AnkiDroid/src/main/java/com/ichi2/anki/utils/ext/Flow.kt

@@ -87,8 +87,8 @@ fun <T> StateFlow<T>.launchCollectionInLifecycleScope(block: suspend (T) -> Unit
         activity.lifecycle.repeatOnLifecycle(Lifecycle.State.STARTED) {
             this@launchCollectionInLifecycleScope.collect {
                 // on re-resume, an unchanged value will be emitted for a StateFlow
-                if (lastValue == value) return@collect
-                lastValue = value
+                if (lastValue == it) return@collect
+                lastValue = it
                 if (isRobolectric) {
                     HandlerUtils.postOnNewHandler { runBlocking { block(it) } }
                 } else {