feat: Output JSON logs to stdout

[sirewix]

Part of Structured logging to stdout · famedly/team-workflows#46

[emgrav]

maybe a bit late to make this suggestion, but maybe it makes more sense to just allow users to choose the formatter rather than just a json boolean? We might want to use the extra pretty print in tests fx

just a thought, don't let it block merging if you disagree

[sirewix]

@emgrav
It could be a nice feature, but I think default json vs not json should be enough for now. And it's not a breaking change, I explicitly set default to be false.

As for the tests, I don't think we should init the whole otel stack in there, it spams extra "cannot export something something" errors. We use traced_test in some crates, seem to work ok and is pretty easy to bootstrap

[codecov]

Codecov Report

Attention: Patch coverage is 92.30769% with 1 line in your changes missing coverage. Please review.

Project coverage is 80.70%. Comparing base (53dec92) to head (1ebf726).
Report is 1 commits behind head on main.

✅ All tests successful. No failed tests found.

Files with missing lines	Patch %	Lines
src/lib.rs	85.71%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main       #7      +/-   ##
==========================================
+ Coverage   80.50%   80.70%   +0.19%     
==========================================
  Files           4        4              
  Lines         277      285       +8     
==========================================
+ Hits          223      230       +7     
- Misses         54       55       +1     

Files with missing lines	Coverage Δ
src/config.rs	100.00% <100.00%> (ø)
src/lib.rs	86.63% <85.71%> (-0.27%)	⬇️

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 53dec92...1ebf726. Read the comment docs.