Description

Cypress integration tests are hitting the production environment on GH actions triggered by a PR. Example of failing PR checks due to changes in a page structure here. This flow defeats the idea of having an early notification of issues, and its testing code changes are not related to the current PR. There are two primary alternatives to fix this issue.
1 - Move the integration tests to merge to master trigger, pointing to QA instead of production. Instead.
2 - Run Cypress tests against a local server at GH actions and keep them as part of the PR checks.

I propose to move most of the tests to option 2 and move tests that require a full running environment to option 1(if any)