chore: bump cypress to v 11

[eschutho]

SUMMARY

Per the cypress docs, this experimental flag should help with some of the chromium memory problems we've been seeing, but it needs at least v12 in order to do anything:
https://docs.cypress.io/guides/references/error-messages#The-Chromium-Renderer-process-just-crashed

Bumping this version to 11. We'll do 12 in a separate PR

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

• Has associated issue:
• Required feature flags:
• Changes UI
• Includes DB Migration (follow approval process in SIP-59)
  • Migration is atomic, supports rollback & is backwards-compatible
  • Confirm DB migration upgrade and downgrade tested
  • Runtime estimates and downtime expectations provided
• Introduces new feature or API
• Removes existing feature or API

[villebro]

Nice, let's hope this fixes that flaky test! One comment on the removed config.

[villebro]

Was this removal intentional? I don't see it mentioned in the docs or the description..

[eschutho]

Yeah, it was flagged by typescript that it no longer exists.

[villebro]

Oh ok, that explains why it wasn't mentioned in the docs 😄

[eschutho]

I checked to see if we had tried this flag before, and sure enough @rusackas had a PR that enabled it, and then removed it because it wasn't supported in v10. (they added support in v12). So I'm trying my luck to see how easily I can bump to 12. 🤞

[villebro]

LGTM, thanks for working on this ❤️

[rusackas]

I think there's a way to upgrade with a GUI using npx if you're not already aware. I've been curious how well that works, maybe it'll be helpful for the next bumps.

[rusackas]

[eschutho]

I think there's a way to upgrade with a GUI using npx if you're not already aware. I've been curious how well that works, maybe it'll be helpful for the next bumps.

Oh nice. I'll try that. There's also a PR already where someone did the difficult work of bumping to v13. I was thinking of reviving that PR.