Remove option dbg.dump

[sim642]

It's described as "Dumps the results to the given path" and it is some kind of strange override for outfile ("File to print output to.").

[Copilot]

Pull request overview

This PR removes the dbg.dump option (a special-case output redirection mechanism) and simplifies result/log output routing to use the normal outfile/standard channels instead.

Changes:

• Removed dbg.dump handling from CLI initialization (maingoblint.ml), including its special override behavior.
• Removed dbg.dump from the JSON options schema and eliminated Messages.get_out (which depended on dbg.dump).
• Updated result/log output code paths to write directly to the configured output channels (!Messages.out, stderr, etc.) without per-component dump files.

Reviewed changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
src/maingoblint.ml	Removes runtime handling for dbg.dump and simplifies CIL/timing output channel selection.
src/framework/xsltResultOutput.ml	Removes dbg.dump-based output indirection; writes XSLT output to !Messages.out.
src/framework/control.ml	Removes get_out usage and prints globals directly to !M.out.
src/framework/analysisResultOutput.ml	Removes get_out usage; outputs results to !Messages.out.
src/config/options.schema.json	Removes the dbg.dump option from the schema.
src/common/util/messages.ml	Deletes Messages.get_out, which implemented dbg.dump-based per-file output.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 7 out of 7 changed files in this pull request and generated no new comments.