Support different target platforms for modules in AnalyzerFacade

Instead of reusing the same AnalyzerFacade that is used for resolution
of a module to resolve its dependencies, analyze each dependency
module/library with a facade depending on its target platform. Introduce
and use CommonLibraryDetectionUtil in addition to
KotlinJavaScriptLibraryDetectionUtil, to detect common libraries (with
.kotlin_metadata files).

Note that before multi-platform projects, this was not needed because
there were only two platforms (JVM and JS), and JVM module had only JVM
modules/libraries as dependencies, JS module had only JS
modules/libraries as dependencies. Now, for example, a JVM module can
have a common module/library as a dependency, and it would be incorrect
to analyze that dependency with JvmAnalyzerFacade because that facade
does not know anything about .kotlin_metadata files.

The changes in Dsl.kt and KotlinCacheServiceImpl.kt are needed because
PsiElement.getJavaDescriptorResolver, called from some IDE code, started
to fail on a common module, because the container for a common module
does not have the JavaDescriptorResolver

idea/testData/multiModuleHighlighting/multiplatform/catchHeaderExceptionInPlatformModule/common/common.kt

@@ -0,0 +1,3 @@
+package test
+
+class MyException : Exception()

idea/testData/multiModuleHighlighting/multiplatform/catchHeaderExceptionInPlatformModule/jvm/jvm.kt

@@ -0,0 +1,10 @@
+package test
+
+fun test(f: () -> Unit) {
+    try {
+        f()
+    }
+    catch (e: MyException) {
+        f()
+    }
+}