add another docker layer upon the basic rw image with debug tools

[lmatz]

when trying to generate a CPU flame graph in a RW cluster, @MrCroxx suggested that

maybe we can add another docker layer upon the basic rw image with debug tools?

try to gather what debug tools are needed except the toolchain for CPU flame graph, please leave a message

we can create another build image pipeline on Buildkite later

[BugenZhao]

I had an attempt before: #12588, including GDB, LLDB, and debugging symbols.

I'm happy if someone would continue working on that.

[BugenZhao]

I had an attempt before: #12588, including GDB, LLDB, and debugging symbols.

The motivation is somehow different: I was focusing on offline debugging there. For example, download the core dump from the production container, then import it into the corresponding debug image. Users will continue to deploy using the original image.

Here we mentioned "flame graph", so it's actually online debugging. It appears that we have to include those debug tools in the production image itself.

[lmatz]

#14432 related but for debugging external systems instead of risingwave itself, just leave a record here

[github-actions]

This issue has been open for 60 days with no activity. Could you please update the status? Feel free to continue discussion or close as not planned.