chore: do not rely on transitive dep. from npm/react

[lmiller1990]

• Closes N/A

User facing changelog

N/A

Additional details

I removed an unused dependency from npm/react, cypress-plugin-snapshots. Surprisingly, things broke. It turned out we were relying on a transitive dependency, which isn't ideal.

cypress-plugin-snapshots -> socket.io-client -> engine.io-client

I added the required dependency to app and launchpad. This still isn't ideal. We do patch-package in socket, as well as nohoist - I don't think there should be any socket.io related dependencies at the top level node_modules at all. I am unsure why there are there at all. I could not figure out why after a whole day, so I'm leaving it here - this is at least better than relying on a dependency's dependency, especially one that isn't even in packages.

Steps to test

Observe CI passes - this confirms nothing is broken.

How has the user experience changed?

PR Tasks

• Have tests been added/updated?
• 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?
• 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.

[lmiller1990]

I think I can do this as the same time as Vite 3: #22915 Let's see!

[lmiller1990]

Doing this in here: https://github.com/cypress-io/cypress/pull/22915/files