[IR] Dump IdSignatures and mangled names in irText tests

The reason #1 for this feature is that we want to test IdSignatures
generated for declarations. Currently, there is no (easy) way to ensure
that a change in the signature building logic doesn't cause any breaking
changes wrt klibs.

Now, most IdSignatures include hashed mangled names in them, so even if
we catch a regression where the included hash changes, there would be no
way of knowing immediately what caused it, unless we'd also have mangled
names in the expectations.

The reason #2 is to test the manglers themselves. Currently, there are
no tests for them. They heavily duplicate each other, this is already
causing issues (see KT-57427) that would be very hard to catch without
these tests.

^KT-58238 Fixed

compiler/testData/ir/irText/js/dynamic/implicitCastFromDynamic.sig.kt.txt

@@ -0,0 +1,38 @@
+// CHECK:
+//   Mangled name: {}d
+//   Public signature: /d|5174763769109925331[0]
+val d: dynamic
+  // CHECK JS_IR NATIVE:
+  //   Mangled name: #<get-d>(){}
+  //   Public signature: /d.<get-d>|-6701718004621354461[0]
+  get
+
+// CHECK:
+//   Mangled name: {}p
+//   Public signature: /p|6715504260787941082[0]
+val p: Int
+  // CHECK JS_IR NATIVE:
+  //   Mangled name: #<get-p>(){}
+  //   Public signature: /p.<get-p>|-1162552463316289847[0]
+  get
+
+// CHECK JS_IR NATIVE:
+//   Mangled name: #test1(<dynamic>){}
+//   Public signature: /test1|4353482563436034667[0]
+fun test1(d: dynamic): Int
+
+// CHECK JS_IR NATIVE:
+//   Mangled name: #test2(<dynamic>){}
+//   Public signature: /test2|-7945586224410659921[0]
+fun test2(d: dynamic): Any
+
+// CHECK JS_IR NATIVE:
+//   Mangled name: #test3(<dynamic>){}
+//   Public signature: /test3|8250122632028727853[0]
+fun test3(d: dynamic): Any?
+
+// CHECK JS_IR NATIVE:
+//   Mangled name: #test4(<dynamic>){}
+//   Public signature: /test4|3998898222236566906[0]
+fun test4(d: dynamic): String
+