Fix HelperScanner: treat field/method types as USES not REQUIRES

The JVM only eagerly resolves superclass and interfaces during
defineClass. Field types, method parameter/return types, and declared
exceptions are resolved lazily. Marking them as REQUIRES created false
dependency cycles that broke topological sort ordering when injecting
large helper batches (2000+ classes).

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

Author: jbachorik

dd-java-agent/agent-tooling/src/main/java/datadog/trace/agent/tooling/HelperScanner.java

@@ -156,7 +156,10 @@ public FieldVisitor visitField(
       final String descriptor,
       final String signature,
       final Object value) {
-    record(Type.getType(descriptor), REQUIRES);
+    // Field types are resolved lazily by the JVM, not during defineClass.
+    // Using USES (not REQUIRES) avoids false dependency cycles that can break
+    // topological sort ordering for superclass/interface relationships.
+    record(Type.getType(descriptor), USES);
     return null;
   }
 
@@ -167,8 +170,11 @@ public MethodVisitor visitMethod(
       final String descriptor,
       final String signature,
       final String[] exceptions) {
-    record(Type.getMethodType(descriptor), REQUIRES);
-    record(exceptions, REQUIRES);
+    // Method parameter/return types and declared exceptions are resolved lazily
+    // by the JVM, not during defineClass. Only superclass and interfaces are
+    // eagerly resolved, which are handled by visit().
+    record(Type.getMethodType(descriptor), USES);
+    record(exceptions, USES);
     return methodScanner;
   }