[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/expressions/breakContinueInWhen.sig.kt.txt

@@ -0,0 +1,30 @@
+// CHECK:
+//   Mangled name: #testBreakDoWhile(){}
+//   Public signature: /testBreakDoWhile|-1704674514591918334[0]
+fun testBreakDoWhile(): Unit
+
+// CHECK:
+//   Mangled name: #testBreakFor(){}
+//   Public signature: /testBreakFor|-7772840210562213149[0]
+fun testBreakFor(): Unit
+
+// CHECK:
+//   Mangled name: #testBreakWhile(){}
+//   Public signature: /testBreakWhile|3882710933639253522[0]
+fun testBreakWhile(): Unit
+
+// CHECK:
+//   Mangled name: #testContinueDoWhile(){}
+//   Public signature: /testContinueDoWhile|-1939470436794612956[0]
+fun testContinueDoWhile(): Unit
+
+// CHECK:
+//   Mangled name: #testContinueFor(){}
+//   Public signature: /testContinueFor|-6520729324717708312[0]
+fun testContinueFor(): Unit
+
+// CHECK:
+//   Mangled name: #testContinueWhile(){}
+//   Public signature: /testContinueWhile|2151596509430082894[0]
+fun testContinueWhile(): Unit
+