Cypress tests fail right away on a PR coming from a fork

[HonkingGoose]

Describe the bug

Contributing to our project from a fork is not really working smoothly right now.
Cypress test fail with a message about the --record flag.

Give the steps to reproduce

1. Create fork of octoclairvoyant-webapp
2. Make changes on a new branch within the fork
3. Open a PR upstream
4. Cypress tests run (after first-time contributor approval)
5. Cypress tests fail with:

   You passed the --record flag but this project has not been setup to record.
   
   This project is missing the 'projectId' inside of 'cypress.json'.
   
   We cannot uniquely identify this project without this id.
   
   You need to setup this project to record. This will generate a unique 'projectId'.
   
   Alternatively if you omit the --record flag this project will run without recording.

What browsers are you seeing the problem on?

Bug is not about browser

Have you thought of a possible solution?

Yes

If you have thought of a solution, please tell us about it!

Maybe we can distinguish between internal PRs and outsider PRs, and change things so we only run Cypress with the --record flag on internal PRs?

Do you want to help fix the bug?

No

Is there anything else we need to know?

Example of a PR coming from a fork: #563

[Belco90]

Which command are you using to run the E2E tests?

Ah sorry, this is when running the CI. I'll have to check what's the best way to deal with this.