Tech debt - centralize mock data used for patterns

[adamwhitlock1]

User Story

As an engineer it should be easy to access specific repeated pieces of mock data that are frequently used for the various tasks.

Background

user data like name, dob, ssn, address, and prefill core data could be centralized to reduce the amount of changes that need to happen to make a prototype functional.

One suggested approach could be to further seperate the mock data folder to have a common data section to use within mock server and also things like the e2e tests, static data prototypes ex. post-study route, or other places that may arrise.

We have used a specific set of data for the most part throughout our pattern work and the repeated code could be slimmed down and make maintenance of these prototypes easier.

ACs

• data is centralized and can be changed 'once' to reflect across prototypes
• ideally this data changing also does not break tests

Review needed by

• VA Product Owner
• Product Manager
• UX Research Team
• Engineering Team

Definition of Done

• Documentation has been updated, if applicable.
• Acceptance Criteria in related issue are met.
• Reviewers have approved.

[adamwhitlock1]

We have merged in the updates for this ticket and it can be closed now. There is a single source of truth for our user data and we can now change it in one place and see it reflected throughout our prototypes.