Test User Account Dashboard Backend CRUD Functions

[bramleyjl]

Issue Description

• The TUD app will be updated to include CRUD functionality for vets-api user accounts, accessible by the frontend as API endpoints as well as by the population Rake task. Interactions with external service providers, especially MPI, will have to be handled on their end (their teams develop test account information creation via an endpoint) or mocked on our end.

  Tasks

• [ ] CRUD API endpoints exist that can parse fields/values and translate them into creating, reading, updating, and deleting Test User Accounts and the related vets-api account.
• [ ] A CRUD API request will trigger API calls to update the same test user in the external services (or mock) where that user has or will have external information
• [ ] The population rake task will invoke the CRUD methods to create, update, and delete vets-api accounts

Acceptance Criteria

• [ ] Users using the TUD frontend will be able to create, read, update, and delete custom vets-api accounts

• [ ] vets-api accounts can be created, updated, and deleted via the DB population script

  How to configure this issue

• [ ] Attached to a Milestone (when will this be completed?)
• [ ] Attached to an Epic (what body of work is this a part of?)
• [ ] Labeled with Team (product support, analytics-insights, operations, service-design, tools-be, tools-fe)
• [ ] Labeled with Practice Area (backend, frontend, devops, design, research, product, ia, qa, analytics, contact center, research, accessibility, content)
• [ ] Labeled with Type (bug, request, discovery, documentation, etc.)

[bramleyjl]

After conducting research and interfacing with external service providers we have determined that programmatic test account CRUD operations is not possible at this time and will not be included in the MVP.