chore: move server e2e tests to system-tests

[JessicaSachs]

• For Support system testing environment #16207

Additional details

• Initial PR to move the e2e tests to system tests, to decrease the chances for merge conflicts on the rest of the work for Support system testing environment #16207
• Creates a @tooling/system-tests package (currently at /system-tests but may move to /tooling/system-tests)
  • Before: yarn workspace @packages/server test-e2e foo_spec
  • After: yarn workspace @tooling/system-tests test foo_spec
• Moved the e2e tests and snapshots to that package
• Discovered that a lot of tests were failing snapshot checks and still passing: https://app.circleci.com/pipelines/github/cypress-io/cypress/24784/workflows/96ac48fc-bda7-439b-870b-8984f2de6a59/jobs/924253/steps
  • 4531644 appears to have fixed this somehow
    • this is because it removed the erroneous implementation of the fix for allowDuplicate.
    • I fixed the patch up properly in 946803e and this appears to let ALL snapshots properly validate again, even ones using allowDuplicate
  • this is why there are snapshot/test updates for some tests
  • opened Fix warning when projectRoot is not writable #18485 to resolve legitimate non_root_read_only_fs_spec failure
• In the interest of getting this in develop, two issues have been created to explore the 2 test suites that are still having issues:
  • error_ui_spec Fix error_ui system test #18497
  • studio_spec Fix studio_spec system tests #18498

PR Tasks

• Have tests been added/updated?
• [na] Has the original issue or this PR been tagged with a release in ZenHub?
• [na] Has a PR for user-facing changes been opened in cypress-documentation?
• [na] Have API changes been updated in the type definitions?
• [na] Have new configuration options been added to the cypress.schema.json?

[cypress-bot]

Thanks for taking the time to open a PR!

• Create a Draft Pull Request if your PR is not ready for review. Mark the PR as Ready for Review when you're ready for a Cypress team member to review the PR.
• Become familiar with the Code Review Checklist for guidelines on coding standards and what needs to be done before a PR can be merged.

[cypress]

---

Test summary

18552 • 0 • 214 • 7 • 1

---

Run details

Project	cypress
Status	Passed
Commit	3bd122a
Started	Oct 18, 2021 7:39 PM
Ended	Oct 18, 2021 7:52 PM
Duration	13:28 💡
OS	Linux Debian - 10.9
Browser	Multiple

View run in Cypress Dashboard ➡️

---

Flakiness

	cypress/integration/cypress/proxy-logging-spec.ts		1
1	Proxy Logging > request logging > xhr log has response body/status code

---

This comment has been generated by cypress-bot as a result of this project's GitHub integration settings. You can manage this integration in this project's settings in the Cypress Dashboard

[lmiller1990]

Cool @JessicaSachs. Excited for this. Can you give a hint at what file(s) to review, or how we can write a system test for a CT project? With 600+ files changed, it's hard to know where to start looking. Is there any high-priority-must-review files?