Random 403's on lower environments can cause spurious test failures in Cypress.

[ndouglas]

Description

Occasionally, Cypress tests fail on lower environments with an HTTP 403. At first, I assumed that this was due to a fluke or an issue with attempting to edit a locked node. However, attempting to edit a locked node will result in a 200, not a 403.

The only 403's I see after multiple tests are those resulting from attempting to load Google Tag Manager, which fails (possibly always) on lower environments.

I should find some way to exclude these requests so that they don't cause spurious test failures and waste engineer time.

Acceptance Criteria

• Requests to GTM.js no longer result in 403's, or some other method of resolving this issue has been found.

[ndouglas]

Closed by #12747.