dbex/103053-cypress-tests-for-0781: first draft of basic 0781 flow

[sethdarragile6]

This PR adds basic cypress tests and fixture data for the new 0781 workflow.

Are you removing, renaming or moving a folder in this PR?

• No, I'm not changing any folders (skip to TeamSites and delete the rest of this section)
• Yes, I'm removing, renaming or moving a folder

Did you change site-wide styles, platform utilities or other infrastructure?

• No
• Yes, and I used the proxy-rewrite steps to test the injected header scenario

Summary

• (Summarize the changes that have been made to the platform)
  This PR adds basic cypress tests and fixture data for the new 0781 workflow.
• (If bug, how to reproduce)
• (What is the solution, why is this the solution)
• (Which team do you work for, does your team own the maintenance of this component?)
  Disability Benefits Experience Team 1 (DBEX-TREX) 🦖
• (If using a flipper, what is the end date of the flipper being required/success criteria being targeted)

Related issue(s)

• Link to ticket created in va.gov-team repo
  [0781] Cypress tests - "End to End" UI testing va.gov-team#103053
• Link to previous change of the code/bug (if applicable)
  department-of-veterans-affairs/vets-website#0000
• Link to epic if not included in ticket
  department-of-veterans-affairs/va.gov-team#0000

Testing done

• added new end to end tests for the 0781 flow

Screenshots

Non-UI changes only.
Note: This field is mandatory for UI changes (non-component work should NOT have screenshots).

What areas of the site does it impact?

(Describe what parts of the site are impacted if code touched other areas)

Acceptance criteria

Quality Assurance & Testing

• I fixed|updated|added unit tests and integration tests for each feature (if applicable).
• No sensitive information (i.e. PII/credentials/internal URLs/etc.) is captured in logging, hardcoded, or specs
• Linting warnings have been addressed
• Documentation has been updated (link to documentation *if necessary)
• Screenshot of the developed feature is added
• Accessibility testing has been performed

Error Handling

• Browser console contains no warnings or errors.
• Events are being sent to the appropriate logging solution
• Feature/bug has a monitor built into Datadog or Grafana (if applicable)

Authentication

• Did you login to a local build and verify all authenticated routes work as expected with a test user

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?