Add logging for submit 0781 job exhaustion

[ajones446]

This PR adds logging for when the submit0781 job exhausts, in order to be consistent with how we log exhaustion for the BDD instructions and Veteran Upload jobs.

This change is part of a larger effort to gradually migrate to using the Lighthouse API instead of EVSS. All the migration behavior is behind flippers.

Summary

• *This work is behind a feature toggle (flipper): YES
• (Summarize the changes that have been made to the platform)
• (If bug, how to reproduce)
• (What is the solution, why is this the solution?)
• (Which team do you work for, does your team own the maintenance of this component?) DBEX Team 2 (Carbs)
• (If introducing a flipper, what is the success criteria being targeted?)

Related issue(s)

• This Issue: #97122
• Initial Datadog setup and testing issue #95698
• Initial 0781 PR 83846 disability benefits migrate 0781 uploads to lighthouse #19186
• Veteran Upload logging PR 83845 nb disability benefts migrate submit uploads to lighthouse #19182

Testing done

• New code is covered by unit tests
• Describe what the old behavior was prior to the change
  The job exhausted but did not log to Datadog
• Describe the steps required to verify your changes are working as expected. Exclusively stating 'Specs run' is NOT acceptable as appropriate testing
  This will be monitored in Datadog
• If this work is behind a flipper:
  • Tests need to be written for both the flipper on and flipper off scenarios. Docs.
  • What is the testing plan for rolling out the feature?
    The 0781 LH migration is being rolled out incrementally based on a percentage of production users, starting at 1%. All 0781 upload attempts will be logged and monitored.

Screenshots

Note: Optional

What areas of the site does it impact?

(Describe what parts of the site are impacted andifcode touched other areas)

Acceptance criteria

• I fixed|updated|added unit tests and integration tests for each feature (if applicable).
• No error nor warning in the console.
• Events are being sent to the appropriate logging solution
• Documentation has been updated (link to documentation)
• No sensitive information (i.e. PII/credentials/internal URLs/etc.) is captured in logging, hardcoded, or specs
• Feature/bug has a monitor built into Datadog (if applicable)
• If app impacted requires authentication, did you login to a local build and verify all authenticated routes work as expected
• I added a screenshot of the developed feature

Requested Feedback

(OPTIONAL)What should the reviewers know in addition to the above. Is there anything specific you wish the reviewer to assist with. Do you have any concerns with this PR, why?

[NB28VT]

Small style comments but they aren't important feel free to merge

[NB28VT]

lol

[NB28VT]

Totally optional style not but I like these in a before block under the context block, as it sets up all the tests for this context and if we add more it will make that easier. Super nitpicky though

[NB28VT]

Also a nit, this is more like sidekiq_job_exhaustion_arguments or something like that hmm I don't have a better name but since it has the job id and job args its more like metadata

[NB28VT]

Bahhh that's right we don't know which form actually failed here (0781 or 0781a) but since we're logging the same metric regardless and logging the actual error below it doesn't matter, so I think this is totally fine

[ajones446]

Yeah, that was my thinking as well. If we need to dig into the error more, we can find the form type on the submission.