Log payload when job ends

This would have been useful for replaying events-from-token-change
failures and just seems like it might be useful generally at no cost.
Yes, definitely - the benefit is not just that splunk can parse it easily, but more importantly that we have a consistent logging format! That way, when you write something that parses the logs in one way, you can easily use it in other contexts. Additionally, if we use kayvee and we decide to use some tool that expects the logs in a different format, we can change the kayvee library instead of having to change things everywhere