feat(logging): add lualogging compatible logging

[Tieske]

This is a minimum implementation. Should it add more debug level logging in places?

[Tieske]

example output:

Tieskes-MBP:pegasus.lua thijs$ lua example/copas.lua
Fri Sep 13 09:29:42 2024 DEBUG Handler created, without location
Fri Sep 13 09:29:42 2024 INFO Pegasus is up on http://localhost:9090
Fri Sep 13 09:29:42 2024 DEBUG Handler created, without location
Fri Sep 13 09:29:42 2024 INFO Pegasus is up on https://localhost:9091
Fri Sep 13 09:30:01 2024 INFO Request for: GET /index.html
Fri Sep 13 09:30:01 2024 INFO Request for: GET /style.css
Fri Sep 13 09:30:01 2024 INFO Request for: GET /1.jpg
Fri Sep 13 09:30:17 2024 INFO Request for: POST /index.html
Fri Sep 13 09:30:25 2024 INFO Request for: GET /index.html
Fri Sep 13 09:30:34 2024 INFO Request for: GET /api/1v0/people/John
Fri Sep 13 09:30:34 2024 DEBUG served John's data
Fri Sep 13 09:30:43 2024 INFO Request for: GET /api/1v0/people/Mary
Fri Sep 13 09:30:43 2024 ERROR 'Mary' is an unknown person
Fri Sep 13 09:33:35 2024 INFO Request for: GET /downloads/1.jpg
Fri Sep 13 09:33:58 2024 INFO Request for: POST /index.html
Fri Sep 13 09:34:07 2024 INFO Request for: GET /index.html

[EvandroLG]

Super nice PR, @Tieske :)
I just didn't get why you're passing the log through the Handler. Wouldn't it be simpler to directly call the log module in the relevant modules, or is there something I'm overlooking?

[Tieske]

to be able to set it per handler. Otherwise it would become a global. In case you are serving multiple server sockets and would like separate logging.

for example create 2 loggers with the following log patterns:

    "%date %level [server1] %message (%source)"

    "%date %level [server2] %message (%source)"

And then pass those to the handlers of the 2 server sockets we're handling (note that %date, %level, %message and %source are placeholders that will be replaced by the actual log data). This would cleanly identify the source of the loglines, even if sent to the same log destination)