[ML] Account for service being triggered twice in tests (#80000)

A race can cause the service under test to be triggered twice.
As the test is asserting that the trigger occurs at least once multiple
invocations should not be considered a failure

Author: davidkyle

x-pack/plugin/ml/src/test/java/org/elasticsearch/xpack/ml/MlDailyMaintenanceServiceTests.java

@@ -34,6 +34,7 @@
 import org.elasticsearch.xpack.core.ml.job.config.Job;
 import org.junit.After;
 import org.junit.Before;
+import org.mockito.Mockito;
 import org.mockito.stubbing.Answer;
 
 import java.util.Collections;
@@ -149,10 +150,10 @@ private void assertThatBothTasksAreTriggered(Answer<?> deleteExpiredDataAnswer,
             latch.await(5, TimeUnit.SECONDS);
         }
 
-        verify(client, times(2)).threadPool();
-        verify(client).execute(same(DeleteExpiredDataAction.INSTANCE), any(), any());
-        verify(client).execute(same(GetJobsAction.INSTANCE), any(), any());
-        verify(mlAssignmentNotifier).auditUnassignedMlTasks(any(), any());
+        verify(client, Mockito.atLeast(2)).threadPool();
+        verify(client, Mockito.atLeast(1)).execute(same(DeleteExpiredDataAction.INSTANCE), any(), any());
+        verify(client, Mockito.atLeast(1)).execute(same(GetJobsAction.INSTANCE), any(), any());
+        verify(mlAssignmentNotifier, Mockito.atLeast(1)).auditUnassignedMlTasks(any(), any());
         verifyNoMoreInteractions(client, mlAssignmentNotifier);
     }