test: don't assume a tick rate in Reactive.TestLogging (#1285)

The test asserted at least 5 ticks while a 100 ms Sleep runs, i.e. that each
10 ms wait of tickWhileRunning() returns on time. A loaded macOS runner took
~33 ms per wait and failed with 3 ticks (master run 42389941988, 6b8e68c).
The test checks that the observer counts match the tick count; the only
guaranteed minimum is 2 ticks (one RUNNING, the final SUCCESS).

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>

Author: facontidavide

tests/gtest_reactive.cpp

@@ -157,7 +157,9 @@ TEST(Reactive, TestLogging)
   ASSERT_EQ(ret, NodeStatus::SUCCESS);
 
   int num_ticks = counters[0];
-  ASSERT_GE(num_ticks, 5);
+  // At least one RUNNING tick (Sleep) and the final SUCCESS tick. The exact
+  // count depends on how long each wait takes, which varies on loaded CI runners.
+  ASSERT_GE(num_ticks, 2);
 
   ASSERT_EQ(observer.getStatistics("testA").success_count, num_ticks);
   ASSERT_EQ(observer.getStatistics("success").success_count, num_ticks);