Merge together MultiplatformHighlighting and MultiplatformAnalysis tests

Basically, the former uses an old quickly-scrapped infrastructure,
which were not applicable for HMPP, so  the latter tests were written.

So, both check for one and the same thing (highlighting in MPP projects),
but MultiplatformAnalysisTest is more modern,
and has a lot of inconvenient stuff in MultiplatformHighlighting fixed
^KT-43116 Fixed

idea/testData/multiplatform/transitiveDependencyOnCommonSourceSets/commonMpp/common.kt

@@ -1,7 +1,7 @@
 package test
 
-expect class Expect {
-    fun commonFun(): String
+expect class <!LINE_MARKER("descr='Has actuals in JVM'")!>Expect<!> {
+    fun <!LINE_MARKER("descr='Has actuals in JVM'")!>commonFun<!>(): String
 }
 
 fun topLevelCommonFun(): Int = 42

idea/testData/multiplatform/transitiveDependencyOnCommonSourceSets/jvmMpp/jvm.kt

@@ -1,7 +1,7 @@
 package test
 
-actual class Expect {
-    actual fun commonFun(): String = ""
+actual class <!LINE_MARKER("descr='Has declaration in common module'")!>Expect<!> {
+    actual fun <!LINE_MARKER("descr='Has declaration in common module'")!>commonFun<!>(): String = ""
 
     fun platformFun(): Int = 42
 }

idea/testData/multiplatform/transitiveDependencyOnCommonSourceSets/nonMpp/nonMpp.kt

@@ -1,6 +1,6 @@
 package test
 
-fun main() {
+fun <!LINE_MARKER!>main<!>() {
     val e = Expect()
 
     e.platformFun()