Submit claim vets-api client/service work

[kjduensing]

Issue Description

Context

This ticket defines implementing the vets-api endpoint for creating a claim and adding an expense, as well as implementing the client & service code for calling the submit endpoint on the travel pay API (below).

Essentially the wrapper logic for:

• Creating a claim - #92324
• Adding an expense - #92329
• Submitting the claim - #92256

Impact

Doing this will allow us to submit a claim for the Veteran.

Notes

• The idea is to not make vets-website call 3-4 endpoints to submit a claim, though that could be valid, comment below if you prefer one way or the other.

Endpoint Path

• Local: POST http://localhost:3000/travel_pay/v0/claims
• Staging: https://staging-api.va.gov/travel_pay/v0/claims
• Production: https://api.va.gov/travel_pay/v0/claims

Response Schema

{
  claimId: UUID
}

Back end tasks

• [ ] Client code written - calls correct endpoint
• [ ] Service code written - transforms/processes response from client
  • [ ] Handle errors
• [ ] Controller endpoint written
• [ ] Config
  • [ ] settings.test.yml updated if needed
  • [ ] settings.local.yml updated if needed
  • [ ] settings.yml updated if needed
  • [ ] infra-manifests updated if needed
  • [ ] dev
  • [ ] staging
  • [ ] prod
• [ ] Tests written
  • [ ] Unit
  • [ ] Happy path
  • [ ] Exhaustive failure paths
  • [ ] Integration
  • [ ] VCR Cassettes
  • [ ] Betamocks registration
• [ ] Mock data
• [ ] Testing
  • [ ] Unit tests pass
  • [ ] QA testing - try to break it in staging
• [ ] Improve 1 thing about the codebase
• [ ] Swagger docs updated

Acceptance Criteria

• [ ] Backend tasks complete
• [ ] I can hit the endpoint defined above using postman or another testing tool and see the response defined above

[ayush-chak]

Hey team! Please add your planning poker estimate with Zenhub @hinzed1127 @kjduensing @liztownd