[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/contextReceivers/overloadPriority.sig.kt.txt

@@ -0,0 +1,30 @@
+// CHECK:
+//   Mangled name: Context
+//   Public signature: /Context|null[0]
+class Context {
+  // CHECK:
+  //   Mangled name: Context#<init>(){}
+  //   Public signature: /Context.<init>|-5645683436151566731[0]
+  constructor() /* primary */
+
+}
+
+// CHECK JVM_IR:
+//   Mangled name computed from Ir:         #f(Context){}kotlin.String
+//   Mangled name computed from Descriptor: #f!Context(){}kotlin.String
+//   Public signature: /f|-5175802051654911360[0]
+fun f($context_receiver_0: Context): String
+
+// CHECK JVM_IR:
+//   Mangled name: #f(){}kotlin.Any
+//   Public signature: /f|-2324325393552926316[0]
+fun f(): Any
+
+// CHECK:
+//   Mangled name: #test(){}
+//   Public signature: /test|6620506149988718649[0]
+fun test(): Unit
+  // CHECK JVM_IR:
+  //   Mangled name: #test(){}#<anonymous>#static@Context(){}kotlin.Int
+  local fun Context.<anonymous>(): Int
+