It's sometimes more convenient to get coredumps instead of plain stack
traces, especially if you didn't have gdb attached to the process at the
time.

Note that, asymmetrically, we add pl_debug_abort() to the vulkan debug
callbacks but not the opengl debug callbacks. This is motivated by
vulkan debug errors mainly corresponding to API usage violations (should
never happen!), whereas OpenGL debug errors mainly correspond to runtime
errors (e.g. invalid GLSL files), which should not trigger an abort().

(Note that you can also `(gdb) break pl_log_stack_trace`)