Raise positive waitUntil timeouts to 5s for loaded CI runners (#1340)

NoiseCoverageTests' session-callback test failed on the first CI run
that actually executed it (every run since it landed had hung and been
killed before completion): onSessionEstablished fires via
DispatchQueue.global().async, and the test waited only 0.5s — fine on
a dev machine, too tight on a loaded CI runner saturated by parallel
test workers.

Raise every positive-wait timeout from 0.5s to 5s (matching
TestConstants.defaultTimeout) across the suites that poll for async
callbacks. waitUntil returns as soon as the condition holds, so
passing runs are unaffected; only genuine failures wait longer. The
two negative waits in BLEServiceCoreTests ("expect nothing arrives")
deliberately keep their short windows.

Co-authored-by: jack <jackjackbits@users.noreply.github.com>
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

bitchatTests/Noise/NoiseCoverageTests.swift

@@ -542,7 +542,7 @@ struct NoiseCoverageTests {
 
         let didEstablish = await TestHelpers.waitUntil(
             { establishedRecorder.establishedCount == 2 },
-            timeout: 0.5
+            timeout: 5.0
         )
         #expect(didEstablish)
         #expect(establishedRecorder.establishedPeerIDs.contains(alicePeerID))
@@ -561,7 +561,7 @@ struct NoiseCoverageTests {
 
         let didFail = await TestHelpers.waitUntil(
             { failureRecorder.failureCount == 1 },
-            timeout: 0.5
+            timeout: 5.0
         )
         #expect(didFail)
         #expect(failingManager.getSession(for: charliePeerID) == nil)