Fix flaky cron trigger test by closing context before assertions

The "schedule trigger test according to cron expression" test was flaky
because the cron expression (every 5 seconds) could fire a second time
between blockUntilExecute() returning and the assertTraces() call
completing, producing 3 or 4 traces instead of the expected 2.

Fix by closing the Spring application context immediately after the
first execution completes, before entering the expect block. The
ScheduledTasksEndpoint bean reference is captured before closing so
the endpoint assertion in the and: block still works.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: bm1549

dd-java-agent/instrumentation/spring/spring-scheduling-3.1/src/latestDepTest/groovy/SpringSchedulingTest.groovy

@@ -25,8 +25,12 @@ class SpringSchedulingTest extends InstrumentationSpecification {
     setup:
     def context = new AnnotationConfigApplicationContext(TriggerTaskConfig, SchedulingConfig)
     def task = context.getBean(TriggerTask)
+    def scheduledTaskEndpoint = context.getBean(ScheduledTasksEndpoint)
 
     task.blockUntilExecute()
+    // Close the context immediately after the first execution to prevent a second cron
+    // firing before assertions complete, which would produce extra traces and cause flakiness.
+    context.close()
 
     expect:
     assert task != null
@@ -54,13 +58,10 @@ class SpringSchedulingTest extends InstrumentationSpecification {
       }
     }
     and:
-    def scheduledTaskEndpoint = context.getBean(ScheduledTasksEndpoint)
     assert scheduledTaskEndpoint != null
     scheduledTaskEndpoint.scheduledTasks().getCron().each {
       it.getRunnable().getTarget() == TriggerTask.getName()
     }
-    cleanup:
-    context.close()
   }
 
   def "schedule interval test"() {

dd-java-agent/instrumentation/spring/spring-scheduling-3.1/src/test/groovy/SpringSchedulingTest.groovy

@@ -25,8 +25,12 @@ class SpringSchedulingTest extends InstrumentationSpecification {
     setup:
     def context = new AnnotationConfigApplicationContext(TriggerTaskConfig, SchedulingConfig)
     def task = context.getBean(TriggerTask)
+    def scheduledTaskEndpoint = context.getBean(ScheduledTasksEndpoint)
 
     task.blockUntilExecute()
+    // Close the context immediately after the first execution to prevent a second cron
+    // firing before assertions complete, which would produce extra traces and cause flakiness.
+    context.close()
 
     expect:
     assert task != null
@@ -54,13 +58,10 @@ class SpringSchedulingTest extends InstrumentationSpecification {
       }
     }
     and:
-    def scheduledTaskEndpoint = context.getBean(ScheduledTasksEndpoint)
     assert scheduledTaskEndpoint != null
     scheduledTaskEndpoint.scheduledTasks().getCron().each {
       it.getRunnable().getTarget() == TriggerTask.getName()
     }
-    cleanup:
-    context.close()
   }
 
   def "schedule interval test"() {