Increase timeout for flaky async test

If executed standalone
OnCodeOwnerApprovalIT#changeMessageListsNewlyApprovedPaths_async
succeeds 100 out of 100 times, however if it is executed as part of
running all tests it sometimes fails because the expected change message
didn't appear within the 1s timeout. To make the test less flaky
increase the timeout to 3s.

Signed-off-by: Edwin Kempin <ekempin@google.com>
Change-Id: Ia4933d6c2ceae0cea742d86f19c088dc62156609

javatests/com/google/gerrit/plugins/codeowners/acceptance/api/OnCodeOwnerApprovalIT.java

diff --git a/javatests/com/google/gerrit/plugins/codeowners/acceptance/api/OnCodeOwnerApprovalIT.java b/javatests/com/google/gerrit/plugins/codeowners/acceptance/api/OnCodeOwnerApprovalIT.java
index 06e4c15..d31cbfb 100644
--- a/javatests/com/google/gerrit/plugins/codeowners/acceptance/api/OnCodeOwnerApprovalIT.java
+++ b/javatests/com/google/gerrit/plugins/codeowners/acceptance/api/OnCodeOwnerApprovalIT.java
@@ -1199,7 +1199,7 @@
     return RetryerBuilder.<T>newBuilder()
         .retryIfException(t -> true)
         .withStopStrategy(
-            StopStrategies.stopAfterDelay(Duration.ofSeconds(1).toMillis(), MILLISECONDS))
+            StopStrategies.stopAfterDelay(Duration.ofSeconds(3).toMillis(), MILLISECONDS))
         .build()
         .call(() -> assertion.call());
   }