[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/declarations/annotations/classLiteralInAnnotation.sig.kt.txt

@@ -0,0 +1,40 @@
+// CHECK:
+//   Mangled name: A
+//   Public signature: /A|null[0]
+open annotation class A : Annotation {
+  // CHECK:
+  //   Mangled name: A{}klass
+  //   Public signature: /A.klass|6015918431206184939[0]
+  val klass: KClass<*>
+    // CHECK JVM_IR:
+    //   Mangled name: A#<get-klass>(){}kotlin.reflect.KClass<*>
+    //   Public signature: /A.klass.<get-klass>|5739372350059323846[0]
+    // CHECK JS_IR NATIVE:
+    //   Mangled name: A#<get-klass>(){}
+    //   Public signature: /A.klass.<get-klass>|4259458871347467473[0]
+    get
+
+  // CHECK:
+  //   Mangled name: A#<init>(kotlin.reflect.KClass<*>){}
+  //   Public signature: /A.<init>|5783844857148764471[0]
+  constructor(klass: KClass<*>) /* primary */
+
+}
+
+// CHECK:
+//   Mangled name: C
+//   Public signature: /C|null[0]
+class C {
+  // CHECK:
+  //   Mangled name: C#<init>(){}
+  //   Public signature: /C.<init>|-5645683436151566731[0]
+  constructor() /* primary */
+
+}
+
+// CHECK:
+//   Mangled name: #test1(){}
+//   Public signature: /test1|4297044443957252634[0]
+@A(klass = C::class)
+fun test1(): Unit
+