[CST] Pass tracked item id to submit5103 method

[jerekshoe]

Summary

Lighthouse has added the ability for us to pass a tracked item ID when making a request to the claims/5103 endpoint. This PR updates the controller method and service to pass the correct JSON body when making the call to Lighthouse

• This work is behind a feature toggle (flipper): YES

Related PR(s)

• [CST] Pass tracked item id to submit5103 vets-website#31771

Related issue(s)

• [CST] Pass tracked item id to Lighthouse when submitting 5103 evidence waiver va.gov-team#91457

Testing done

Updated specs to account for the fact that we are passing a tracked item ID to the submit5103 method now

• 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?

[aherzberg]

LGTM for mobile changes

[tpharrison]

LGTM

[github-actions]

Backend-review-group approval confirmed.