DBEX/92496: add transactionId to LH Submit request bodies

[aurora-a-k-a-lightning]

Summary

• This work is behind a feature toggle (flipper): YES
• add meta.transactionId to LH submit endpoint requests

Related issue(s)

• add transactionId to the LH synchronous request va.gov-team#92496

Testing done

• New code is covered by unit tests
• use updated test harness to send submit request to LH staging environment or follow this:

1. have a Form526Submission on hand as @submission (i.e. @submission = Form526Submission.first)
2. @transform_service = EVSS::DisabilityCompensationForm::Form526ToLighthouseTransform.new
3. @body = @transform_service.transform(@submission.form['form526'])
4. @service = BenefitsClaims::Service.new(@submission.user_account.icn)
5. this is the new part

transaction_id = @submission.auth_headers['va_eauth_service_transaction_id']
@response = @service.submit526(@body, nil, nil, { generate_pdf:, transaction_id: })

6. at this point you can check @service.send(:prepare_submission_body, @body.as_json) to see the meta in the request body
7. or check @response.body['meta'] to see what you sent to lighthouse

Screenshots

What areas of the site does it impact?

Form526 2022 form version submission to lighthouse

Acceptance criteria

• I updated 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

[freeheeling]

Should ({data: {type:, attributes}}) be updated to include the new format that includes the addition of meta: { transaction_id: } to the request body? attributes also appears to be be missing a colon at the end.

[aurora-a-k-a-lightning]

drat. great point! i'll address this in refactor. thank you, @freeheeling

[freeheeling]

Looks good, with one question concerning a code comment.

[github-actions]

Backend-review-group approval confirmed.