Store error backtraces on discrete executions

[Intrepidd]

Closes #1162

[bensheldon]

This is awesome and super clean 👍🏻

Would you want to also render this out into the Dashboard view too in this PR?

Otherwise I have one tiny suggestion, and the test that fails is a flake, so this looks awesome 🎉

[Intrepidd]

Thanks for the swift review !

Would you want to also render this out into the Dashboard view too in this PR?

You can already kinda see it in the details of an execution in the _good_job_execution key.

I figured this is good enough for this PR and could be released as-is to provide some value, but if you have pointers on how you would like it to be displayed as a first class citizen, I'm glad to make a PR for it

[bensheldon]

No sweat! I was poking around to form an opinion and just did it 😁

Thank you for working on this. It's great!

[Earlopain]

This is pretty neat, thanks for working on this👍

If I am understanding this corretly, the cleaned backtrace will be saved and only the first frame displayed, is that correct? There have been several occasions where my application backtrace didn't include the full context, for one or another reason.

Would it make sense to store the full backtrace and format only on display? I'm thinking of something like how Rails displays errors in development. Edit: openend #1328