fix(tests): make EventCorrelatorTest timestamps deterministic

Avoid relying on Thread.sleep(100) to produce distinct timestamps.

The sleep was removed because the test only requires timestamp ordering,
not elapsed time. However, the Windows Bazel build showed that
OffsetDateTime.now() can return identical timestamps in consecutive calls
depending on the environment clock resolution.

Advance the timestamp explicitly instead, keeping the test deterministic
across different platforms.

Author: flrnd

extended/src/test/java/io/kubernetes/client/extended/event/EventCorrelatorTest.java

@@ -144,17 +144,16 @@ void eventCorrelate(
       Boolean expectedSkip)
       throws Exception {
     EventCorrelator correlator = new EventCorrelator();
+    OffsetDateTime now = OffsetDateTime.now();
     for (CoreV1Event event : previousEvents) {
-      OffsetDateTime now = OffsetDateTime.now();
       event.setFirstTimestamp(now);
       event.setLastTimestamp(now);
       Optional<MutablePair<CoreV1Event, V1Patch>> result = correlator.correlate(event);
       if (result.isEmpty()) {
         correlator.updateState(event);
       }
     }
-    Thread.sleep(100);
-    OffsetDateTime now = OffsetDateTime.now();
+    now = now.plusNanos(10);
     newEvent.setFirstTimestamp(now);
     newEvent.setLastTimestamp(now);
     Optional<MutablePair<CoreV1Event, V1Patch>> result = correlator.correlate(newEvent);