Unify output of all tools

[JBludau]

@ethan-puyaubreau and me want to discuss if it makes sense to factor out how the results are printed by the tools.
right now this is coded into the tools directly but it should be factored out. This way users could specify at configure time or runtime if they want .xml, csv, json, sql ...

We think the tools in general would benefit from this. @vlkale @dalg24

[ethan-puyaubreau]

Indeed, right now the way the tools print results is hard-coded directly within each tool. I believe it makes a lot of sense to factor out this output logic. This would give them much greater flexibility in how they consume and use the results.

Beyond just the output format, we also think it's important to decouple measurement mechanisms (like time tracking) from the data formatting and export logic. For example, the core mechanism for measuring execution time is fundamentally the same regardless of how that time data is ultimately presented. By separating these concerns, users could format the measured data in any way they want without needing to re-code the measurement logic every time.

[vlkale]

Yes, this makes sense and sounds like a good direction to me. I think this unification / streamlining of printed output from tools would also help for testing tools with Google Tests.

Google Test generally doesn't work well with output from printf's.

[vlkale]

Yes, this makes sense and sounds like a good direction to me. I think this unification / streamlining of printed output from tools would also help for testing tools with Google Tests.

Google Test generally doesn't work well with output from printf's.