chore: update app to cypress-example-kitchensink v5.0.0

[MikeMcC399]

Additional details

Updates https://github.com/cypress-io/cypress/tree/gh-pages for publication to https://example.cypress.io

Sourced from [email protected]

Steps to test

After merge:

URL	Expect
https://example.cypress.io/commands/actions	In the type() section there should be a space after each //
https://example.cypress.io/commands/misc	In the cy.exec() section else { should be on a separate line
https://example.cypress.io/commands/storage	In cy.getAllLocalStorage() the properties prop1 - prop3 should not be quoted. Same for cy.getAllSessionStorage() with prop3 - prop6
https://example.cypress.io/commands/waiting	Check that the paragraph "More information:" is displayed correctly
https://example.cypress.io/commands/window	Check that the page appears correct

How has the user experience changed?

Minor visible changes on https://example.cypress.io

PR Tasks

• [na] Have tests been added/updated?
• [na] Has a PR for user-facing changes been opened in cypress-documentation?
• [na] Have API changes been updated in the type definitions?

[jennifer-shehane]

@MikeMcC399 For this update - we have scripts that we run on release that will update the gh-pages branch - so this doesn't need to be done directly.

cypress/guides/release-process.md

Line 164 in a0a4eb1

16. If needed, deploy the updated [`cypress-example-kitchensink`][cypress-example-kitchensink] to `example.cypress.io` by following [these instructions under "Deployment"](../packages/example/README.md).

You should just need to bump our dependency of the cypress-example-kitchensink dep and we will handle the build/deploy.

[MikeMcC399]

@jennifer-shehane

I ran the script

yarn workspace @packages/example deploy

to update the gh-pages locally through a PR. This is a bit safer than doing it directly, as otherwise you push directly to the website without seeing what you're doing.

Also the Circleci script was accidently deleted by @AtofStryker so it needs to be put back again.

It's up to you if you want to process this PR, which should produce correct results, or if you want to handle it manually on your side. Your decision.

[MikeMcC399]

I will leave this PR in draft until after the Cypress 14.5.0 release. Either the release process will have handled this update and the PR will be obsolete, or if this didn't happen properly, then this PR can be activated.

The changes are in any case non-critical.