Increase Flaky Timeout in testIlmHistoryIndexCanRollover (elastic#62353) (elastic#62402)

This busy assert easily takes about 5s on a very fast work station
so the default of 10s is not sufficient here at all.

Author: original-brownbear

x-pack/plugin/ilm/src/internalClusterTest/java/org/elasticsearch/xpack/ilm/ILMHistoryTests.java

@@ -29,6 +29,7 @@
 import java.util.Arrays;
 import java.util.Collection;
 import java.util.Collections;
+import java.util.concurrent.TimeUnit;
 
 import static org.elasticsearch.cluster.metadata.IndexMetadata.SETTING_NUMBER_OF_REPLICAS;
 import static org.elasticsearch.cluster.metadata.IndexMetadata.SETTING_NUMBER_OF_SHARDS;
@@ -115,7 +116,7 @@ public void testIlmHistoryIndexCanRollover() throws Exception {
                 //instead of failing the whole test change it to assertion error and wait some more time
                 fail(e.getMessage());
             }
-        });
+        }, 1L, TimeUnit.MINUTES);
 
         //make sure ILM is stopped so no new items will be queued in ILM history
         assertTrue(client().execute(StopILMAction.INSTANCE, new StopILMRequest()).actionGet().isAcknowledged());