Add deterministic reproduction delay to Spring scheduling cron test

After closing the Spring context (which stops the scheduler), add a sleep
longer than the cron interval to prove that no extra traces appear even
under worst-case timing. This makes the previously-flaky race condition
fully deterministic: without context.close(), the sleep guarantees extra
cron executions; with it, the scheduler is stopped and assertions pass.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: bm1549

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

@@ -33,6 +33,9 @@ class SpringSchedulingTest extends InstrumentationSpecification {
     // 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()
+    // Deterministic reproduction: sleep longer than the cron interval (5 s) to prove
+    // that closing the context stopped the scheduler and no extra traces appear.
+    Thread.sleep(6000)
 
     expect:
     assert task != null

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

@@ -33,6 +33,9 @@ class SpringSchedulingTest extends InstrumentationSpecification {
     // 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()
+    // Deterministic reproduction: sleep longer than the cron interval (5 s) to prove
+    // that closing the context stopped the scheduler and no extra traces appear.
+    Thread.sleep(6000)
 
     expect:
     assert task != null