Cypress integration test workflow

[IGallupSoCo]

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

Summary

• A manual workflow has been created to support the troubleshooting of CI failures in a more time-efficient way. The user provides inputs for the relevant product directory within src/applications and specifies the branch. The workflow then takes those inputs and runs any Cypress specs that can be found anywhere within the specified directory. The workflow runs are considerably simpler and shorter than in vets-website CI, and should enable engineers to identify patterns behind e2e test failures more quickly, and to rapidly test any attempted fixes as they are added to a given branch.

Related issue(s)

• Link to ticket created in va.gov-team repo
  Ticket 1
  Ticket 2
  Ticket 3
• Link to epic if not included in ticket
  Platform Reliability Team Epic 85944

What areas of the site does it impact?

This adds a manual workflow and one supporting shell file.

Acceptance criteria

Quality Assurance & Testing

• 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 design doc)

[rmessina1010]

LGTM