SPIKE: do not run browse e2e specs in pr's #377
Description
Story
as of #371, the browse specs are running against the actual api. to prevent so many calls to the api from being made, we should investigate whether there is a way to make the current "browse.cy.js" file only run in CI against the main branch. not on pull requests. OR, if there's a way to only trigger the spec to run when the api is updated.
if it is possible, we could then create another browse spec that intercepts the api calls and tests for the same things. this would ensure that as we develop, we aren't knowingly breaking things. the version of the browse spec that calls the api would help us make sure that no api updates cause us any issues either.
Acceptance Criteria
- [ ]