Tech discovery on mock data for vets-api E2E tests

[nanotone]

Investigate the feasibility of using mock data to facilitate test data setup for vets-api E2E tests (e.g. Max CFI hyphenated conditions).

Background: historically, EE team has used staged data for E2E testing of new features. This generally involves going through the frontend UI for both VA.gov Staging and VBMS UAT to create/update the Veterans, claims, rated disabilities, etc. needed for E2E scenarios. However, this can be an arduous process, especially the VBMS UAT part. For features that don't entail behavior change or verification outside of VA.gov, mock data may be an easier option.

Timebox to 1 day.

Not included in this work

• Actually setting up mock data for E2E tests

Notes about work

• vets-api-mockdata repo -- note that E2E-specific mock data will most likely not live in this repo, but may have to be "consistent" (i.e. user IDs, etc) with other existing mock data.

[nanotone]

Opening and closing this ticket due to team discussion and agreement that we should use staged data after all, due to uncertainties about what realistic hyphenated codes look like in the case of analogous codes (i.e. for unlisted conditions).