Updates to slog to make it the default feature-full logger

[samlaf]

Started looking into slog:

• https://go.dev/blog/slog
• https://www.youtube.com/watch?v=8rnI2xLrdeM

and agree with @dmanc at this point that we should probably start adopting slog as our standard logger everywhere. Been playing with it a bit and our current interface is super limiting wrt what can be done with slog (for eg can't pass a context to logging functions right now, which can be used to also log traceIds). The blog above mentions this

This draft PR is a wip for adding features to the slogger itself. But we'll eventually need to find a way to adapt our main interface, probably in a next PR. This will require more discussions.

Features added thus far:

• Only print required log level (production logger will only print info and above logs, whereas the development one will also print debug logs) 4c03592 Found a much easier way to do this: df441e7
• Separate constructor into two, one for TextHandler and one for JsonHandler (I'm personally becoming a big fan of golang's key-value text format) 52c50b7
• Print proper source file information (see image below*) 52c50b7
• make the slog logger an embedded struct (instead of named field) so that we have access to its method. Also return the SLogger struct instead of Logger interface from constructors so that users can use those methods (.WithGroup for eg) d5b616a

• because of our log interface and structs that wrap the underlying logger, the srouce information getting printed was always the wrapper location, instead of its caller, which is useless:
  

[dmanc]

Another thing that could be nice is to have the option to write logs to a file in addition to stdout.

[samlaf]

Another thing that could be nice is to have the option to write logs to a file in addition to stdout.

Check bded386
Made the io.Writer an argument to the constructors. So to write to both stdout and a file, you can just pass a io.MultiWriter(os.Stdout, file).

[shrimalmadhur]

I feel this should expect a log config which should have: env, log level etc - whatever is needed.

[samlaf]

Shall we take the entire slog.HandlerOptions as input then?
So NewSlogTextLogger(outputWriter io.Writer, handerOptions slog.HandlerOptions)

[ian-shim]

I think that makes sense or something like

type SLoggerConfig struct {
 slog.HandlerOptions
 OutputWriter io.Writer
}

@shrimalmadhur wdyt?

[samlaf]

See 2bfeb3f

[ian-shim]

nit: // prints this level and above

[samlaf]

78e783b

[ian-shim]

I think that makes sense or something like

type SLoggerConfig struct {
 slog.HandlerOptions
 OutputWriter io.Writer
}

@shrimalmadhur wdyt?