Fix Byte Buddy use in debug jar

The `shadow` configuration extends `api` now, which means that all
the `api`-style dependencies of this module are not bundled in the
fat jar and are instead mentioned in the POM file as `RUNTIME`
dependencies.

This means that now JNA is not included with the jar, but when
someone depends on the jar to later call `DebugProbes.install()`,
JNA is fetched as a transitive dependency.

This is what we want: JNA is not needed in the jar, because when
the debugger is run as a Java agent, attachment of Byte Buddy
happens in `Installer`, and JNA-based attach emulation is not used;
Byte Buddy is also written is such a way that if JNA is not in the
class path, nothing breaks unless one tries to use attach
emulation.

Author: dkhalanskyjb

kotlinx-coroutines-debug/build.gradle

@@ -14,7 +14,7 @@ configurations {
      * but in that case it changes dependency type to "runtime" and resolves it
      * (so it cannot be further modified). Otherwise, shadow just ignores all dependencies.
      */
-    shadow.extendsFrom(compile) // shadow - resulting configuration with shaded jar file
+    shadow.extendsFrom(api) // shadow - resulting configuration with shaded jar file
     configureKotlinJvmPlatform(shadow)
 }
 
@@ -24,8 +24,8 @@ dependencies {
     shadowDeps "net.bytebuddy:byte-buddy-agent:$byte_buddy_version"
     compileOnly "io.projectreactor.tools:blockhound:$blockhound_version"
     testCompile "io.projectreactor.tools:blockhound:$blockhound_version"
-    runtime "net.java.dev.jna:jna:$jna_version"
-    runtime "net.java.dev.jna:jna-platform:$jna_version"
+    api "net.java.dev.jna:jna:$jna_version"
+    api "net.java.dev.jna:jna-platform:$jna_version"
 }
 
 jar {