chore: re-name dashboard references to Cypress Cloud

[astone123]

• Closes Rebrand dashboard to cloud #24386

User facing changelog

n/a

Additional details

We are now referring to dashboard as Cypress Cloud. This PR updates all of the wording around the dashboard to use "Cypress Cloud" instead. I also updated some internal variable names to say "cloud" rather than "dashboard".

Steps to test

The most important thing to test is that all Cypress Cloud actions still work with these changes. Verify the following:

• You can still log into Cypress Cloud
• The "connect project" modal flow still works
• Runs tab still links to the correct runs
• Latest runs, flaky badges, and average duration still appear on the specs list
• Other cloud integration things that I'm forgetting

Also verify that all visible copy refers to Cypress Cloud (not dashboard) and follows the brand standards

PR Tasks

• Have tests been added/updated?
• [na] Has the original issue (or this PR, if no issue exists) been tagged with a release in ZenHub? (user-facing changes only)
• Has a PR for user-facing changes been opened in cypress-documentation? Update all text references of Dashboard to Cloud cypress-documentation#4719
• [na] Have API changes been updated in the type definitions?

[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.

[CLAassistant]

All committers have signed the CLA.

[cypress]

---

Test summary

9288 • 0 • 1483 • 0 • 6

---

Run details

Project	cypress
Status	Passed
Commit	30c12f0
Started	Nov 17, 2022 1:50 PM
Ended	Nov 17, 2022 2:07 PM
Duration	17:19 💡
OS	Linux Debian -
Browser	Multiple

View run in Cypress Dashboard ➡️

---

Flakiness

	e2e/origin/cookie_behavior.cy.ts		4
1	... > same site / cross origin > XMLHttpRequest > sets cookie on same-site request if withCredentials is true, and attaches to same-site request if withCredentials is true
2	... > same site / cross origin > fetch > sets same-site cookies if "include" credentials option is specified from request, but does not attach same-site cookies to request by default (same-origin)
3	... > same site / cross origin > XMLHttpRequest > sets cookie on same-site request if withCredentials is true, and attaches to same-site request if withCredentials is true
4	... > same site / cross origin > fetch > sets same-site cookies if "include" credentials option is specified from request, but does not attach same-site cookies to request by default (same-origin)
	commands/xhr.cy.js		1
1	src/cy/commands/xhr > abort > aborts xhrs currently in flight
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

[lmiller1990]

Looks good - I left one nit, but not really a big deal.

If you did just want to rename without re-running CI, you can commit with a commit message containing skip ci and it won't run. https://circleci.com/docs/skip-build/#skipping-a-build

[amehta265]

Everything looks good locally and percy looks good to!