ADFA-4484 Fix flawed KeyedDebouncingActionTest debounce window test

The previous test scheduled three different string keys ("first",
"second", "third"), which created three independent channel entries
rather than coalescing — causing all three actions to fire.

Replace with a test that schedules the same key twice with a delay
shorter than the debounce window, verifying the window resets and
the action fires exactly once.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: yaturner

common/src/test/java/com/itsaky/androidide/utils/KeyedDebouncingActionTest.kt

@@ -54,21 +54,20 @@ class KeyedDebouncingActionTest {
     }
 
     @Test
-    fun `last value wins when multiple sends arrive before debounce window`() = runBlocking {
-        val received = CopyOnWriteArrayList<String>()
+    fun `late reschedule of same key extends debounce window and fires exactly once`() = runBlocking {
+        val count = AtomicInteger(0)
         val debouncer = KeyedDebouncingAction<String>(
             scope = makeScope(),
-            debounceDuration = 100.milliseconds,
-            action = { key, _ -> received.add(key) }
+            debounceDuration = 150.milliseconds,
+            action = { _, _ -> count.incrementAndGet() }
         )
 
-        debouncer.schedule("first")
-        debouncer.schedule("second")
-        debouncer.schedule("third")
-        delay(400)
+        debouncer.schedule("k")
+        delay(80)              // before debounce fires
+        debouncer.schedule("k") // resets the debounce window
+        delay(500)
 
-        // Since the channel is CONFLATED, only the most-recently sent value survives
-        assertThat(received).hasSize(1)
+        assertThat(count.get()).isEqualTo(1)
         debouncer.cancelAll()
     }