JPS plugin: Cleanup dependencies

- Some unnecessary dependencies are dropped
- `api` is replaced with `implementation` when it's more appropriate (in
  our case more appropriate everywhere). `implementation` makes it
  easier to analyze dependencies because it doesn't export the
  dependencies
- Regarding: `// Workaround for Gradle dependency resolution error`.
  Actually, it's not longer needed for the successful project import.
  Confirmed by Yahor and tested locally.

jps/jps-common/build.gradle.kts

@@ -5,22 +5,22 @@ plugins {
 }
 
 dependencies {
-    api(kotlinStdlib())
-    compileOnly(project(":kotlin-reflect-api"))
-    testImplementation(project(":kotlin-reflect"))
-    api(project(":compiler:util"))
-    api(project(":compiler:cli-common"))
-    api(project(":compiler:frontend.java"))
-    api(project(":js:js.frontend"))
-    api(project(":native:frontend.native"))
+    implementation(kotlinStdlib())
+    implementation(project(":compiler:util"))
+    implementation(project(":compiler:cli-common"))
+    implementation(project(":compiler:frontend.java"))
+    implementation(project(":js:js.frontend"))
+    implementation(project(":kotlin-reflect"))
     compileOnly(intellijUtilRt())
     compileOnly(intellijPlatformUtil())
     compileOnly(jpsModel())
     compileOnly(jpsModelImpl())
     compileOnly(jpsModelSerialization())
 
-    testApi(jpsModelSerialization())
-    testApi(commonDependency("junit:junit"))
+    testImplementation(project(":compiler:cli-common"))
+    testImplementation(jpsModelSerialization())
+    testImplementation(project(":kotlin-reflect"))
+    testImplementation(commonDependency("junit:junit"))
 }
 
 sourceSets {