Consider simplifying log function interface about roarr HOT 2 OPEN

I know it might be hard to break the compatibilty like that,

but to be honest, it's one of the surprising choice made in roarr...
i feel other logging libs will start with the message, then add the context ....
so i would be in favor of some kind of solution that make that clearer, even if it break the API

from roarr.

it might have come from developer's prior use of Pino.

I found this odd pattern too when using pino, so I had to write a wrapper that translates:

• "string", ...args

to

• { args }, "string"

from roarr.