Comprehensive Test Plan: Create static test users for cypress testing

[keisterj-oddball]

User Story or Problem Statement

As a QA engineer working on the CMS project, I want static test users for cypress tests, so that tests are not responsible for creating the users needed to perform the test.

Description or Additional Context

Currently, all cypress tests begin by doing two things:

1. Programmatically create a test user with the specified roles/permissions
2. Navigate the CMS UI to log in as that user
   The goal of this ticket is to address the first point above. Comprehensive Test Plan: Refactor Cypress Tests to Bypass the Login Page #19641 addresses the first point above.

Steps for Implementation

1. Assess the users/permissions required for existing cypress tests.
2. Create users locally that meet the testing requirements, then export those users using content-sync.
3. Update the cypress-tests.sh and cypress-parallel-tests.sh scripts to import the test users prior to kicking off the cypress tests.
4. Update cypress tests to reference the static test users instead of creating new users.

Acceptance Criteria

• Cypress tests no longer create a dedicated user for each respective test.
• All tests continue to pass on tugboat and BRD.

[keisterj-oddball]

We decided to pivot to a module called "Default Content Deploy" instead of "Content-Sync" due to some technical difficulties. This work will be ongoing as we work out a few challenges related to the pivot.