Job exceptions not properly attached to good_jobs record

[bensheldon]

When there is an exception that is rescued by retry_on or discard_on, it is not consistently available to the GoodJob adapter as an argument, and does not always appear in the good_jobs.error column. This can happen if there are additional *_perform hooks that intercept the return value.

It seems like the only reliable way to access retry_on or discard_on (without monkey-patching them) is to use ActiveSupport::Instrumentation to hook into the events: https://guides.rubyonrails.org/active_support_instrumentation.html#retry-stopped-active-job

Unfortunately, this means having to pass those objects up through a global (like ActiveSupport::Current) and retrieved in the job processor.