org.jetbrains.kotlin.jvm.compiler.ClasspathOrderTest: drop `Ignore`

This ignore isn't necessary anymore because this test is back in the compiler
and it can use compiler testData

jps/jps-plugin/jps-tests/test/org/jetbrains/kotlin/jvm/compiler/ClasspathOrderTest.kt

diff --git a/jps/jps-plugin/jps-tests/test/org/jetbrains/kotlin/jvm/compiler/ClasspathOrderTest.kt b/jps/jps-plugin/jps-tests/test/org/jetbrains/kotlin/jvm/compiler/ClasspathOrderTest.kt
index 0e96039..9b4635e 100644
--- a/jps/jps-plugin/jps-tests/test/org/jetbrains/kotlin/jvm/compiler/ClasspathOrderTest.kt
+++ b/jps/jps-plugin/jps-tests/test/org/jetbrains/kotlin/jvm/compiler/ClasspathOrderTest.kt
@@ -31,7 +31,6 @@
  * To test this, we compile a Kotlin+Java module (in two modes: CLI and module-based) where a runtime Java class was replaced
  * with a "newer" version in sources, and check that this class resolves to the one from sources by calling a method absent in the runtime
  */
-@Ignore("has to be deleted as it seems a compiler test")
 class ClasspathOrderTest : TestCaseWithTmpdir() {
     companion object {
         private val sourceDir = File(KtTestUtil.getTestDataPathBase() + "/classpathOrder").absoluteFile