EffectLoopingWorks: raise BusyWait timeouts to 30s

The default 10s threshold occasionally trips on the SqlServer CI runner
under 12-way parallel test execution. Bumping to 30s gives the workflow
restart + replay cycle more headroom without changing test semantics.

Author: stidsborg

Core/Cleipnir.ResilientFunctions.Tests/TestTemplates/FunctionTests/EffectTests.cs

@@ -1021,8 +1021,8 @@ await elms.CaptureEach(
 
         for (var i = 0; i < 6; i++)
         {
-            await BusyWait.Until(() => flag.Value == i);
-            await cp.BusyWaitUntil(c => c.Status == Status.Suspended);
+            await BusyWait.Until(() => flag.Value == i, maxWait: TimeSpan.FromSeconds(30));
+            await cp.BusyWaitUntil(c => c.Status == Status.Suspended, maxWait: TimeSpan.FromSeconds(30));
             var storedEffects = await effectStore.GetEffectResults(registration.MapToStoredId(id.Instance));
             storedEffects.Any(e => e.Alias == "Before").ShouldBeTrue();
             storedEffects.Any(e => e.Alias == "Loop").ShouldBeTrue();
@@ -1032,7 +1032,7 @@ await elms.CaptureEach(
             await messageWriter.AppendMessage(i.ToString());
         }
 
-        await cp.BusyWaitUntil(c => c.Status == Status.Succeeded);
+        await cp.BusyWaitUntil(c => c.Status == Status.Succeeded, maxWait: TimeSpan.FromSeconds(30));
 
         iterations.SequenceEqual([0, 1, 2, 3, 4, 5]).ShouldBeTrue();
     }