Consider platform compatibility in library usage index

Logic of module dependencies is enhanced to filter out incompatible
common -> platform dependencies. However the reversed index for getting
all modules that use libraries doesn't take this filtering into
account and returns all modules based exclusively on order entries.
This leads to incorrect library dependency calculation.

^KT-44638 Verification pending

idea/testData/multiplatform/platformDependencyInCommon/common/common.kt

@@ -0,0 +1,6 @@
+fun checkCloneableIsAbsent(array: Array<String>) {
+    array.<!UNRESOLVED_REFERENCE!>clone<!>()
+}
+
+@<!UNRESOLVED_REFERENCE!>Metadata<!>
+class MetaUnresolved

idea/testData/multiplatform/platformDependencyInCommon/dependencies.txt

@@ -0,0 +1,10 @@
+// See KT-44638
+
+MODULE jvm { platform=[JVM] }
+MODULE js { platform=[JS] }
+MODULE common { platform=[JVM, JS] }
+
+jvm -> STDLIB_JVM, MOCK_JDK { kind=DEPENDENCY }
+js -> STDLIB_JS { kind=DEPENDENCY }
+common -> STDLIB_COMMON, STDLIB_JVM { kind=DEPENDENCY }
+jvm -> common { kind=DEPENDS_ON }

idea/testData/multiplatform/platformDependencyInCommon/js/js.kt

@@ -0,0 +1,6 @@
+fun checkCloneableIsAbsent(array: Array<String>) {
+    array.<!UNRESOLVED_REFERENCE!>clone<!>()
+}
+
+@<!UNRESOLVED_REFERENCE!>Metadata<!>
+class MetaUnresolved

idea/testData/multiplatform/platformDependencyInCommon/jvm/jvm.kt

@@ -0,0 +1,6 @@
+fun checkCloneable(array: Array<String>) {
+    array.clone()
+}
+
+<!EXPLICIT_METADATA_IS_DISALLOWED!>@Metadata<!>
+class MetaWithError