tech-story: [M3-10569] - Upgrade Cypress from v14.3.0 to v15.4.0

[jdamore-linode]

Description 📝

Upgrades Cypress and related dependencies to their latest versions. Refer to the Cypress changelog to see what's new in v15:

https://docs.cypress.io/app/references/changelog

I'm going to keep this in draft and see how it works in CI, and may push some additional updates to our Dockerfile.

Changes 🔄

• Upgrade Cypress to v15.x
• Upgrade related packages

Scope 🚢

• All customers
• Some customers (e.g. in Beta or Limited Availability)
• No customers / Not applicable

Target release date 🗓️

N/A. Not urgent, but is blocking our upgrade to Vite v7. (See also #12792)

How to test 🧪

We can rely on CI for this.

Author Checklists

As an Author, to speed up the review process, I considered 🤔

👀 Doing a self review
❔ Our contribution guidelines
🤏 Splitting feature into small PRs
➕ Adding a changeset
🧪 Providing/improving test coverage
🔐 Removing all sensitive information from the code and PR description
🚩 Using a feature flag to protect the release
👣 Providing comprehensive reproduction steps
📑 Providing or updating our documentation
🕛 Scheduling a pair reviewing session
📱 Providing mobile support
♿ Providing accessibility support

• I have read and considered all applicable items listed above.

As an Author, before moving this PR from Draft to Open, I confirmed ✅

• All tests and CI checks are passing
• TypeScript compilation succeeded without errors
• Code passes all linting rules

[jdamore-linode]

Little issue with the video uploads on Cypress v15: it used to be that specs that passed didn't get a recording, now we're uploading a 0-byte mp4 for passing specs. Must be some issue with discardPassedTestRecordings, I'll take a look soon

[github-actions]

This PR is stale because it has been open 15 days with no activity. Please attend to this PR or it will be closed in 5 days

[jdamore-linode]

I'm going to cut our losses with the recording issue and just accept the annoyance for now in the interest of unblocking the Vite upgrade as well as M3-10596. Next week I'll take a look to see if it's worth trying to mitigate this from the pipeline, but not sure it'll be worth the effort (cc @bnussman-akamai)

[dwiley-akamai]

Ran clone-linode.spec.ts and create-firewall.spec.ts locally and they passed. Didn't observe any other issues and CI looks good otherwise ✅

[linode-gh-bot]

Cloud Manager UI test results

🔺 5 failing tests on test run #9 ↗︎

❌ Failing	✅ Passing	↪️ Skipped	🕐 Duration
5 Failing	834 Passing	13 Skipped	42m 3s

Details

Failing Tests
	Spec	Test
❌	clone-linode.spec.ts	Cloud Manager Cypress Tests→clone linode » can clone a Linode from Linode details page
❌	access-key.e2e.spec.ts	Cloud Manager Cypress Tests→object storage access key end-to-end tests » "before all" hook for "can create an access key with unlimited access - e2e"
❌	object-storage.e2e.spec.ts	Cloud Manager Cypress Tests→object storage end-to-end tests » "before all" hook for "can create and delete object storage buckets"
❌	smoke-deep-link.spec.ts	Cloud Manager Cypress Tests→smoke - deep links » Go to each route and validate deep links
❌	object-storage-objects-multicluster.spec.ts	Cloud Manager Cypress Tests→Object Storage Multicluster objects » "before all" hook for "can upload, access, and delete objects"

Troubleshooting

Use this command to re-run the failing tests:

pnpm cy:run -s "cypress/e2e/core/linodes/clone-linode.spec.ts,cypress/e2e/core/objectStorage/access-key.e2e.spec.ts,cypress/e2e/core/objectStorage/object-storage.e2e.spec.ts,cypress/e2e/core/general/smoke-deep-link.spec.ts,cypress/e2e/core/objectStorageMulticluster/object-storage-objects-multicluster.spec.ts"