Fix native-image build-time initialization cascade

Changed profiling-scrubber's internal-api dependency from 'api' to
'implementation'. The 'api' scope created a transitive dependency
chain (scrubber→internal-api→dd-trace-api) that exposed tracer
classes through the scrubber's API surface, causing them to
initialize at build time during GraalVM native-image compilation.

Using 'implementation' keeps internal-api as an internal dependency,
preventing the initialization cascade.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

Author: jbachorik

dd-java-agent/agent-profiling/build.gradle

@@ -20,12 +20,12 @@ excludedClassesCoverage += [
 
 dependencies {
   api libs.slf4j
-  api project(':internal-api')
+  implementation project(':internal-api')
 
   api project(':dd-java-agent:agent-profiling:profiling-ddprof')
   api project(':dd-java-agent:agent-profiling:profiling-uploader')
   api project(':dd-java-agent:agent-profiling:profiling-controller')
-  api project(':dd-java-agent:agent-profiling:profiling-scrubber')
+  implementation project(':dd-java-agent:agent-profiling:profiling-scrubber')
   api project(':dd-java-agent:agent-profiling:profiling-controller-jfr')
   api project(':dd-java-agent:agent-profiling:profiling-controller-jfr:implementation')
   api project(':dd-java-agent:agent-profiling:profiling-controller-ddprof')

dd-java-agent/agent-profiling/profiling-scrubber/build.gradle

@@ -5,7 +5,7 @@ minimumBranchCoverage = 0.0
 
 dependencies {
   api libs.slf4j
-  api project(':internal-api')
+  implementation project(':internal-api')
 
   implementation libs.jafar.parser