[JS IR IC] Drop incremental cache after updating a klib set

Enabled Partial Linkage may replace entire IR expressions with a stub
during klib linking and loading. This may break the incremental cache
dependency graph. Dropping incremental cache files after updating klibs
(e.g. update klib version) covers almost all cases which
could not be tracked due to a broken dependency graph.

This patch could be reverted after fixing KT-57347

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

@@ -5,12 +5,12 @@ STEP 0:
     added file: l2.kt
 STEP 1:
     dependencies: lib1-a, lib1-b, lib1-c
-    removed direct depends: l2.kt
+    added file: l2.kt
 STEP 2..3:
     dependencies: lib1-a, lib1-b, lib1-c
     updated imports: l2.kt
 STEP 4:
     dependencies: lib1
-    removed direct depends: l2.kt
+    added file: l2.kt
 STEP 5:
     dependencies: lib1

js/js.translator/testData/incremental/invalidation/splitJoinModule/main/module.info

@@ -1,7 +1,13 @@
 STEP 0:
     dependencies: lib1, lib2
     added file: m.kt
-STEP 1..3:
+STEP 1:
     dependencies: lib1-a, lib1-b, lib1-c, lib2
-STEP 4..5:
+    added file: m.kt
+STEP 2..3:
+    dependencies: lib1-a, lib1-b, lib1-c, lib2
+STEP 4:
+    dependencies: lib1, lib2
+    added file: m.kt
+STEP 5:
     dependencies: lib1, lib2

js/js.translator/testData/incremental/invalidation/splitJoinModule/project.info

@@ -5,13 +5,13 @@ STEP 0:
     dirty js: lib1, lib2, main
 STEP 1:
     libs: lib1-a, lib1-b, lib1-c, lib2, main
-    dirty js: lib1-a, lib1-b, lib1-c, lib2
+    dirty js: lib1-a, lib1-b, lib1-c, main, lib2
 STEP 2..3:
     libs: lib1-a, lib1-b, lib1-c, lib2, main
     dirty js: lib1-b, lib2
 STEP 4:
     libs: lib1, lib2, main
-    dirty js: lib1, lib2
+    dirty js: lib1, lib2, main
 STEP 5:
     libs: lib1, lib2, main
     dirty js: lib1