test: Mark Android UI tests as flaky and increase timeout

- Add the `@FlakyTest` annotation to the `AndroidUiTests` class to indicate that these tests are unstable.
- Double the `ASSERT_WAIT_TIMEOUT_MILLIS` in `ext.kt` from 10,000 to 20,000 milliseconds to provide more time for assertions in UI tests, helping to mitigate flakiness.

Author: softartdev

app/android/src/androidTest/java/com/softartdev/notedelight/ui/AndroidUiTests.kt

@@ -3,6 +3,7 @@ package com.softartdev.notedelight.ui
 import androidx.compose.ui.test.junit4.createAndroidComposeRule
 import androidx.test.espresso.Espresso
 import androidx.test.ext.junit.runners.AndroidJUnit4
+import androidx.test.filters.FlakyTest
 import androidx.test.filters.LargeTest
 import com.softartdev.notedelight.MainActivity
 import leakcanary.DetectLeaksAfterTestSuccess
@@ -13,6 +14,7 @@ import org.junit.rules.RuleChain
 import org.junit.runner.RunWith
 
 @LargeTest
+@FlakyTest
 @RunWith(AndroidJUnit4::class)
 class AndroidUiTests : AbstractJvmUiTests() {
 

ui/test/src/commonMain/kotlin/com/softartdev/notedelight/ext.kt

@@ -12,7 +12,7 @@ import androidx.compose.ui.test.hasTestTag
 import androidx.compose.ui.test.waitUntilDoesNotExist
 import co.touchlab.kermit.Logger
 
-const val ASSERT_WAIT_TIMEOUT_MILLIS: Long = 10_000
+const val ASSERT_WAIT_TIMEOUT_MILLIS: Long = 20_000
 const val MAX_RETRY_ATTEMPTS = 100
 
 inline fun retryUntilDisplayed(