Upload end of log as breadcrumbs, use exceptions and stacktrace

[emmatyping]

In this PR, we change the send-event function to write out more information into the envelope we send via sentry-cli, particularly adding breadcrumbs with the end of the log and giving the stack trace in a format Sentry self-hosted can understand.

Fixes getsentry/team-ospo#54 and getsentry/team-ospo#53
Example issue with this formatting: https://self-hosted.getsentry.net/organizations/self-hosted/issues/227/?query=is%3Aunresolved

Also a cheat sheet for jq arguments:

• -c collapses to 1 line
• -n means null input (we're just constructing JSON, not mangling it)
• -s is "slurp" JSON lines into an array.
• --arg can be used to write object arguments
• --argjson is like --arg, but takes JSON expressions as the argument!

[emmatyping]

For your reading pleasure, here are the relevant docs pages:
https://develop.sentry.dev/sdk/envelopes/#data-model
https://develop.sentry.dev/sdk/event-payloads/
https://develop.sentry.dev/sdk/event-payloads/breadcrumbs/
https://develop.sentry.dev/sdk/event-payloads/exception/
https://develop.sentry.dev/sdk/event-payloads/stacktrace/

[hubertdeng123]

lgtm