junit: Explain why configureAndInstallAgent is called in two places

Author: fmeum

src/main/java/com/code_intelligence/jazzer/junit/AgentConfiguringArgumentsProvider.java

@@ -37,6 +37,9 @@ public Stream<? extends Arguments> provideArguments(ExtensionContext extensionCo
     // FIXME(fmeum): Calling this here feels like a hack. There should be a lifecycle hook that runs
     //  before the argument discovery for a ParameterizedTest is kicked off, but I haven't found
     //  one.
+    // We need to call this method here in addition to the call in FuzzTestExtensions as our
+    // ArgumentProviders need the bootstrap jar on the classpath and there may be no user-provided
+    // ArgumentProviders to trigger the call in FuzzTestExtensions.
     FuzzTestExecutor.configureAndInstallAgent(
         extensionContext, fuzzTest.maxDuration(), fuzzTest.maxExecutions());
     return Stream.empty();

src/main/java/com/code_intelligence/jazzer/junit/FuzzTestExtensions.java

@@ -44,6 +44,9 @@ public void interceptTestTemplateMethod(Invocation<Void> invocation,
       throws Throwable {
     FuzzTest fuzzTest =
         AnnotationSupport.findAnnotation(invocationContext.getExecutable(), FuzzTest.class).get();
+    // We need to call this method here in addition to the call in AgentConfiguringArgumentsProvider
+    // as that provider isn't invoked before fuzz test executions for the arguments provided by
+    // user-provided ArgumentsProviders ("Java seeds").
     FuzzTestExecutor.configureAndInstallAgent(
         extensionContext, fuzzTest.maxDuration(), fuzzTest.maxExecutions());
     // Skip the invocation of the test method with the special arguments provided by