feat(dap): show messages printed via `TRACE_PRINT_LN`

These are triggered for instance by `println` calls in a Rust program and therefore they should be shown in the **DAP**.

Look at the DAP (Debug Adapter Protocol) implementation in the codebase, likely in a `dap` module or server. Find where trace messages from `TRACE_PRINT_LN` are captured and need to be forwarded to the client. Check existing output handling for other messages. The change involves modifying the debug adapter to send these messages as output events. Test by running a Rust program with `println` in the debugger and verifying the output appears in the DAP client.

Written by the indexing model from the issue text.