[JS IR] Update IC depends graph after intrinsics loading

- Remove unused params from compilerWithIC wrapper.
- Move JsIrBackendContext creation logic into separate function
- Introduce and use compiler interface for IC infrastructure

On dirty rebuild we may reload IR from stdlib,
such reloading may affect files with intrinsics and builtins.
As soon as we load only exported symbols, we must track dependencies
for files with intrinsics or builtins as for others.
This patch implements the logic which updates dependencies for
the stdlib files after loading of intrinsics and builtins.

^KT-54323 Fixed

js/js.translator/testData/incremental/invalidation/enumsInInlineFunctions/lib2/l2.0.kt

@@ -0,0 +1,12 @@
+class TestClass100 {
+    enum class TestEnum {
+        A, B
+    }
+}
+
+fun testEnums(): List<Enum<*>> {
+    val enums1 = foo1()
+    val enums2 = foo2()
+
+    return TestClass100.TestEnum.values().toList() + enums1 + enums2
+}

js/js.translator/testData/incremental/invalidation/enumsInInlineFunctions/lib2/l2.3.kt

@@ -0,0 +1,12 @@
+class TestClass2 {
+    enum class TestEnum {
+        A, B
+    }
+}
+
+fun testEnums(): List<Enum<*>> {
+    val enums1 = foo1()
+    val enums3 = foo3()
+
+    return TestClass2.TestEnum.values().toList() + enums1 + enums3
+}

js/js.translator/testData/incremental/invalidation/enumsInInlineFunctions/lib2/module.info

@@ -0,0 +1,19 @@
+STEP 0:
+    dependencies: lib1
+    modifications:
+        U : l2.0.kt -> l2.kt
+    added file: l2.kt
+STEP 1:
+    dependencies: lib1
+    updated imports: l2.kt
+STEP 2:
+    dependencies: lib1
+    updated imports: l2.kt
+STEP 3:
+    dependencies: lib1
+    modifications:
+        U : l2.3.kt -> l2.kt
+    modified ir: l2.kt
+STEP 4:
+    dependencies: lib1
+    updated imports: l2.kt