feat: Add 'slowTestThreshold' and fix this.slow() inside specs

[BlueWinds]

• Closes Cypress should set a mocha slow threshold for more reasonable reporting #447
• Duplicate of feat: Add 'slowTestThreshold' and fix this.slow() inside specs #18371, which targeted 9.0-release rather than develop, since these are not breaking changes.

User facing changelog

• Adds slowTestThreshold config option to customize slow test threshold.
• Changes the default slow test threshold from 75ms (mocha's default) to 10000ms for e2e tests and 250ms for component tests. To restore the old behavior, you can add "slowTestThreshold": 75 to your cypress configuration.

Additional details

A test that executes for longer than the slowTestThreshold time will be highlighted in yellow with the default spec reporter. This is a visual change only - slow tests still pass.

PR Tasks

• Have tests been added/updated? I have added some relevant unit tests, but welcome further suggestions.
• Has the original issue or this PR been tagged with a release in ZenHub?
• Has a PR for user-facing changes been opened in cypress-documentation? Add documentation for new slowTestThreshold config option cypress-documentation#4145
• Have API changes been updated in the type definitions?
• 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

18560 • 0 • 214 • 7 • 6

---

Run details

Project	cypress
Status	Passed
Commit	41a2d1a
Started	Oct 25, 2021 6:05 PM
Ended	Oct 25, 2021 6:21 PM
Duration	16:36 💡
OS	Linux Debian - 10.9
Browser	Multiple

View run in Cypress Dashboard ➡️

---

Flakiness

	commands/net_stubbing_spec.ts		2
1	network stubbing > waiting and aliasing > can timeout waiting on a single request using "alias.request"
2	network stubbing > waiting and aliasing > can timeout waiting on a single request using "alias.request"
	commands/xhr_spec.js		1
1	... > no status when request isnt forced 404
	cypress/proxy-logging-spec.ts		2
1	Proxy Logging > request logging > xhr log has response body/status code
2	Proxy Logging > request logging > xhr log has response body/status code
This comment includes only the first 5 flaky tests. See all 6 flaky tests in the Cypress Dashboard.

---

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

[jennifer-shehane]

Before

After

[jennifer-shehane]

We're going to do a product review next week on this, so hold off on merging until then. I think it will be fine though.

[chrisbreiding]

Looks like some of the files from the unified branch made it into this PR - packages/app, packages/frontend-shared, etc.

[BlueWinds]

Looks like some of the files from the unified branch made it into this PR - packages/app, packages/frontend-shared, etc.

Fixed. I've been having a weird issue where whenever I switch from unified-desktop-gui to a devlop-based branch, the unification work leaves behind a bunch of files. I usually manually remove them, but forgot this time (and then used git commit -a).

[jennifer-shehane]

@BlueWinds I think this is due to the files being generated when you switch to unified - and being part of their .gitignore, but when switching back to develop, those generated files are still there but not part of develop's .gitignore. You could probably just add those files to the develop .gitignore so that you don't have to deal with this.