feat: use charm/logger

[caarlos0]

This uses charmbracelet/log everywhere.

There is the question of what should we do with the breaking changes in logging and recover...

We could keep the old ones and deprecated them, and then add new ones with another names... but I couldn't think of any good names... ideas?

[codecov]

Codecov Report

Merging #116 (71e91c7) into main (d7c49d2) will increase coverage by 3.34%.
The diff coverage is 93.10%.

@@            Coverage Diff             @@
##             main     #116      +/-   ##
==========================================
+ Coverage   72.65%   76.00%   +3.34%     
==========================================
  Files          18       17       -1     
  Lines         918      900      -18     
==========================================
+ Hits          667      684      +17     
+ Misses        197      162      -35     
  Partials       54       54              

Impacted Files	Coverage Δ
git/git.go	61.97% <0.00%> (ø)
options.go	78.89% <66.66%> (ø)
logging/logging.go	100.00% <100.00%> (ø)
ratelimiter/ratelimiter.go	94.87% <100.00%> (ø)
recover/recover.go	95.65% <100.00%> (+0.91%)	⬆️

... and 1 file with indirect coverage changes

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

[aymanbagabas]

This uses charmbracelet/log everywhere.

There is the question of what should we do with the breaking changes in logging and recover...

We could keep the old ones and deprecated them, and then add new ones with another names... but I couldn't think of any good names... ideas?

We could keep using *log.Logger in those. Then use the standard log adapter in charm/log log.StandardLog() in applications using these middlewares