Update 0781 specs to log submission_id and submitted_claim_id

[ajones446]

The 0781 job uses shared API provider logging values. This BDD PR #19217 updated logging to include submission_id as well as submitted_claim_id. This PR updates the specs to match.

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?)
  Disability Benefits team 2, aka Carbs; yes we do own the maintenance of these components

• (If introducing a flipper, what is the success criteria being targeted?)
  A certain amount of submissions will fail on upload to Lighthouse just as they do to EVSS now - it's the same underlying system; however we will be on the look out for new errors that expose bugs on our side or in Lighthouse's benefits documents API.

Related issue(s)

• Link to ticket created in va.gov-team repo OR screenshot of Jira ticket if your team uses Jira
• Link to previous change of the code/bug (if applicable)
  Issue to improve logging: [LH Doc Upload] Improve BDD production monitoring va.gov-team#95604
  Updating logging PR: [Lighthouse Doc Upload Migration] Fix 526 Document Upload provider ID logging #19217
  Original 0781 specs PR: 83846 disability benefits migrate 0781 a uploads to lighthouse #19231
• Link to epic if not included in ticket

Testing done

• New code is covered by unit tests
• Describe what the old behavior was prior to the change
• Describe the steps required to verify your changes are working as expected. Exclusively stating 'Specs run' is NOT acceptable as appropriate testing
• 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?

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?

[github-actions]

Backend-review-group approval confirmed.

[rmtolmach]

@ajones446 I merged this because these tests were failing in master and blocking dev and staging deploys.

[ajones446]

@rmtolmach Thank you, Rebecca! Sorry I missed that logging change that went in yesterday.