chore: update eventemitter2 and vite deps

[lmiller1990]

• Closes n/a

User facing changelog

n/a

Additional details

• lock eventemitter2 version to fix failing CI test (todo-mvc-firefox)
• update vite and remove patch-package

Steps to test

CI should pass, ALL steps, especially test-binary-against-todomvc-firefox and the other binary ones.

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]

This is causing CI to fail, example.

6.4.8 has a breaking change for types. I locked to 6.4.7 for now. Because we did ^6.4.3 before (notice ^) we got the highest 6.4.x.

They've got an open issue: EventEmitter2/EventEmitter2#292

[lmiller1990]

Changed this so we can remove the patch package we had for 3.0.3.

[cypress]

---

Test summary

40028 • 0 • 3346 • 0 • 1

---

Run details

Project	cypress
Status	Passed
Commit	9c902a2
Started	Sep 9, 2022 5:22 AM
Ended	Sep 9, 2022 5:38 AM
Duration	15:18 💡
OS	Linux Debian - 11.3
Browser	Multiple

View run in Cypress Dashboard ➡️

---

Flakiness

	cypress/e2e/e2e/origin/commands/connectors.cy.ts		1
1	cy.origin connectors > .each()

---

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

[cypress-bot]

Released in 10.8.0.

This comment thread has been locked. If you are still experiencing this issue after upgrading to
Cypress v10.8.0, please open a new issue.