Sidekiq: Ensure jobs are idempotent and transactional

[scottsdevelopment]

• https://github.com/sidekiq/sidekiq/wiki/Best-Practices#2-make-your-job-idempotent-and-transactional

We should verify that the Pension Benefit Intake Job is transactional. Our current hypothesis is that it is, however we need to make sure that during failures or reruns, the state continues where it left off and that things such as "email" or "uploads" do not trigger again once they have been set. These kind of issues can occur depending on where in the job the code had failed and when running them again, there should be fail safes and checks to make sure that resuming the job occurs at the correct operations.

• Ensure that a job always completes without additional side effects, the same way when stopping and starting from various points of failure.

[aplatt-coforma]

Hey team! Please add your planning poker estimate with Zenhub @danlim715 @mjknight50 @scottsdevelopment @TaiWilkin @ToddWebDev @wayne-weibel