Create GitHub Action to Run Cypress

[BCerki]

This PR addresses issue:#101

Includes tests? y
Rebased on main address to conflicts? y
Updated docs? y

Proposed changes:

• Add a github action that runs the cypress test

Additional notes:

• There are some comments on an older version of this PR here: test: set up basic github cypress action #102
• Pre-testing, the action builds the whole app. The build action also builds the whole app--any way to avoid this duplication? Added this question to Remove duplication with CI build job and CI cypress job? #104 to address later
• The action sets off Cypress errors but the test still runs so I think that's not a problem? They mention this behaviour in their docs:
  

[BCerki]

The app wouldn't start unless I had these filled out, but these placeholders seem to work

[wenzowski]

Tech debt: let's run something like Sendria so these configured values are real within the testing environment.

[BCerki]

#113

[wenzowski]

I don't think the daemonization was intended. Let's fix that, document tech debt as new issues, and ship this

[wenzowski]

Tech debt: let's run something like Sendria so these configured values are real within the testing environment.

[wenzowski]

Regarding the Additional Notes:
Let's make sure we've got a tech debt card for our CI/CD process that notes our e2e tests should be booting the candidate docker image that we intend to release to production (as a 12 factor app, we should be able to boot the prod image with development or test environment flag set). The cypress errors appear to be due to the fact that we're running headless from inside a runner that does not have access to a gpu. There's probably a way to squelch these, so that should be tracked as tech debt as well. The npm run browserslist --update-db call should probably also be part of our ci config so I'd track that as separate tech debt.