JSON logging, log.S

[ldemailly]

Alternative to https://pkg.go.dev/golang.org/x/exp/slog but handcrafted JSON output instead

• base: ts, level, file, line, msg hand emitted/fast JSON
• extensibility? ie how to make for instance LogRequest also emit individual fields; in structured version: log.S does
• follow up with checking https://github.com/go-json-experiment/json and https://github.com/devnw/ajson and https://github.com/mitchellh/mapstructure - deferred as we don't deserialize ourselves
• use structured log for LogRequest()
• check what to do with panic() - defer, panic will be unstructured for now
• good candidate for fuzzing?
• maybe have a better set than just Str(key,value) and Attr(key,value) that preserves type of some values (numbers - though there are issues with that and NaN, precision etc)

Fixes #21

[codecov]

Codecov Report

Patch coverage: 100.00% and no project coverage change.

Comparison is base (410963b) 100.00% compared to head (2163e6e) 100.00%.

Additional details and impacted files

@@            Coverage Diff            @@
##              main       #22   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            2         2           
  Lines          166       243   +77     
=========================================
+ Hits           166       243   +77     

Impacted Files	Coverage Δ
http_logging.go	100.00% <100.00%> (ø)
logger.go	100.00% <100.00%> (ø)

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[ldemailly]

will merge and do release tags if the fortiotel with 1.9.0-pre1 using the whole chain (log->scli->fortio->fortiotel) works well