refactor: declare instrumentation dependencies directly (#11986)

refactor: declare instrumentation dependencies directly

Instrumentation project paths are already known during configuration.
Wrapping `project(...)` in `providers.provider` adds unnecessary
indirection without providing useful laziness.

Declaring project dependencies directly makes the aggregation logic
clearer and keeps compile-only stub projects out of the resulting JAR.

# Conflicts:
#	dd-java-agent/instrumentation/build.gradle

Co-authored-by: brice.dutheil <brice.dutheil@datadoghq.com>

Author: bric3

dd-java-agent/instrumentation/build.gradle

@@ -90,9 +90,10 @@ subprojects { Project subProj ->
     if (subProj.path != ':dd-java-agent:instrumentation:vertx:vertx-redis-client:vertx-redis-client-stubs'
       && subProj.path != ':dd-java-agent:instrumentation:tibco-businessworks:tibco-businessworks-stubs') {
       // don't include the redis or tibco stubs
-      parent_project.dependencies {
-        addProvider("implementation", providers.provider { project(subProj.path) })
-      }
+      parent_project.dependencies.add(
+        "implementation",
+        parent_project.dependencies.project(path: subProj.path)
+        )
     }
   }