Addressing #639: print stacktrace in logs

[henryxparker]

This is a quick and dirty fix for the weaver.Log not printing stack traces.
I didn't see any tests for the core module so I didn't write any.
Any feedback appreciated

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
2 out of 7 committers have signed the CLA.

✅ Baccata
✅ henryxparker
❌ zetashift
❌ valencik
❌ armanbilge
❌ CJSmith-0141
❌ zainab-ali

---

zainab-ali seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[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.

---

Henry Parker seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[henryxparker]

I don't know why the cla assistant has two comments. Let me know if that is a blocker and what to do about it

Edit: committer and author were different in git, but they're both me, so I changed the commit to reflect that and the second comment can be ignored. I can make a new PR if necessary

[Baccata]

Hey @henryxparker, sorry for putting some eyes on this only now, things were crazy at work when you raised the PR and I totally forgot to go back to it, apologies.

Anyway, the best location to add tests for this feature would probably be here. Chances are you should probably handcraft a stacktrace to make it easy to compare results and expectations

[henryxparker]

Sorry for the long wait. I was laid off for a while and totally forgot that I had made this PR.
Now that everything is settled I'll be working on it again

[Baccata]

@henryxparker thanks for taking the time to come back to this PR !

However, weaver is in the process of being moved to the typelevel organisation, and though I cannot attest to when exactly the move will conclude, it's quite unlikely that I'll issue another release of weaver under the disneystreaming organisation. If it's not too much to ask, I would suggest moving your PR over there.

https://github.com/typelevel/weaver-test

[henryxparker]

Oh sweet, I'll add it there. Could you add something to the README to indicate this move?