Enable LLDB debug info tests on CI

[EFanZh]

This PR tries to enable LLDB debug info tests on CI, so that unintentional changes to LLDB debug info can be detected.

[EFanZh]

I have observed that several tests were broken, which I marked NOT WORKING, and some pretty printing style has changed, not sure if they were intentional.

[rustbot]

r? @Kobzol

rustbot has assigned @Kobzol.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

[Kobzol]

CC @saethlin I remember you having thoughts on how we should run debugger tests on CI. Personally, I would love for our debugger support to improve, of course, but I'm not sure if we actually have someone working on debugging at the moment and if the debugger support is at a reasonable enough level for us to re-enable the tests.

[saethlin]

The problem with the debuginfo tests is that they just run whatever is installed locally (the tracking issue for this problem is #126092). I ran into llvm/llvm-project#70453, which broke lldb for 2 major LLVM releases because upstream failed to backport the fix.

I have an overly negative view of the test suite because my primary interaction with it is discovering that it is completely broken. I'm aware that some people try to justify the current state of it, but I think that's just knee-jerk status quo defense and if someone tried to introduce this test suite today it would not get merged.

I don't actually work on debuginfo generation or Rust debugger support. As far as I'm aware, such work is primarily out-of-tree and mostly we just adjust our code or tests to match whatever upstream does. There is a Zulip stream #t-compiler/debuginfo but it has not had any new messages in the past 5 months.