chore(security): fix 4 vulnerabilities

[aaronleopold]

Additional details

Running yarn audit shows a lot of vulnerabilities. I am currently in the process of trying to trim some of these down in order to satisfy some of the security requirements at my company, and managed to remove 1 critical and 3 high sev vulnerabilities using resolutions. I did try and tackle more, however there were a LOT of breaking changes for a decent amount of them. I tried to find the guidelines for making these kinds of security-focused, dependency upgrades, but didn't find anything specific, so I apologize if I've missed a step or guideline somewhere!

Steps to test

Installation and testing seemed unchanged with these resolutions, and while I am not yet familiar enough with the entire build process for Cypress, I imagine there is not much to test aside from ensuring no incompatibilities have been added that the tests did not otherwise miss.

How has the user experience changed?

Realistically, it shouldn't change UX!

PR Tasks

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

[CLAassistant]

All committers have signed the CLA.

[cypress-app-bot]

• 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.

[jennifer-shehane]

@aaronleopold We have continuous scans of our repos for security vulnerabilities that we address continuously. Can you outline the dependencies that were showing up as critical/high that you were looking to address? As this PR stands, it is adding new dependencies, not updating existing ones so doesn't appear to be addressing any specific security vulnerabilities.