feat: LogArgsSerializer to customize how args are converter to string

[mxab]

Why

The default behaviour in pushLogs stringifies all arguments in a very simple way. This results in potential [object Object] log messages if some one or some third party library decides to put complex logs arguments e.g. console.info({foo: "bar"})

What

This PR extends the faro config with a logArgsSerializer paremeter that allows to override the default behaviour and put in a custom args renderer

fixes #564

Checklist

• Tests added
• Changelog updated
• Documentation updated

[CLAassistant]

All committers have signed the CLA.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[codecapitano]

Hi @mxab can you also add the new property to the core readme please.

Section: Besides the mandatory properties, Faro configuration also supports the following optional properties:

[mxab]

Done, do you want me to squash the changes?

[codecapitano]

Done, do you want me to squash the changes?

Hey Max you don't need to squash them yourself.
We'll squash & merge them via GH.

[codecapitano]

@mxab Great addition thank you so much. 🙏
Thanks for opening the initial issue and implementing the solution as well 🥳

[mxab]

yeah I only executed the linter in the core package. thx

[mxab]

at last the linter approves 😅