Give the reconnection recording test a window that outlives the reconnect

testReconnectionDuringCallRecording kept exhausting all 3 attempts on the
nightly with 'expected Recording but was Reconnecting..'. The recording is
server side and survives the user's reconnect fine; it was the test racing
its own budget. The buddy participant stops the recording 30 seconds after
its start request, the composite recorder alone needs 20-30s to start, and
the drop plus reconnect plus the polling asserts consumed the rest on slow
CI emulators, so the assert ran after the recording legitimately ended.
Raise the window to 90 seconds. The plain recording test already uses 60
without a reconnect in the middle.

Author: andremion

demo-app/src/androidTestE2etestingDebug/kotlin/io/getstream/video/android/tests/ReconnectionTests.kt

@@ -113,9 +113,14 @@ class ReconnectionTests : StreamTestCase() {
             userRobot.joinCall()
         }
         step("AND participant joins the call") {
+            // The recording window counts from the participant's start request, and the
+            // composite recorder alone can take 20-30s to start. The window has to outlive
+            // the drop, the reconnect and the final polling assert on a slow CI emulator,
+            // otherwise the participant stops the recording on schedule before the assert
+            // and the test fails on a recording that legitimately ended.
             participantRobot
                 .setUserCount(participants)
-                .setCallRecordingDuration(30)
+                .setCallRecordingDuration(90)
                 .joinCall(callId, actions = arrayOf(Actions.RECORD_CALL))
         }
         step("AND participant starts recording a call") {