Consider simplifying log function interface

[gajus]

There is no real difference between:

log.info({time: 1}, 'foo');

and

log.child({time: 1}).info('foo');

If we dropper the former API interface, it would make it easier to avoid mistakes such as attempting to pass context as printf parameters.

Great suggestion by @mikeroelens.

The only concern here is that it is a major breaking change with no easy way to add backwards compatibility. I doubt it will be implemented due to the latter reason, but worth considering how we could promote this pattern more.

[eMerzh]

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

[glensc]

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"