fix(component-testing): Fix webpack-dev-server deps validation crash

[dmtrKovalenko]

This fixes issue https://cypress-io.atlassian.net/browse/CT-391

Actually, there was a small problem related to next v10 that was fixed here, but the weird error is coming from webpack-dev-server peer dependencies validation which was crashing this installation.

I cleaned it up a little bit to 1) make sure that we always use real peer dependencies 2) reduce the amount of code and add better types. But I doubt that we need this, nodejs will throw an explicit error if dependencies are missing but we are running this validation on each start for each run on CI and as far I know (not 100% sure) require under try { } catch will always be deoptimized and won't be cached and overall [require](https://kevin.burke.dev/kevin/node-require-is-dog-slow] is a really slow operation. So maybe we can delete this validation? What do you think @JessicaSachs

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

[cypress]

---

Test summary

9394 • 0 • 119 • 3 • 1

---

Run details

Project	cypress
Status	Passed
Commit	3607477
Started	Apr 2, 2021 2:04 PM
Ended	Apr 2, 2021 2:15 PM
Duration	11:35 💡
OS	Linux Debian - 10.5
Browser	Multiple

View run in Cypress Dashboard ➡️

---

Flakiness

	cypress/integration/retries.ui.spec.js		1
1	runner/cypress retries.ui.spec > opens attempt on each attempt failure for the screenshot, and closes after test passes

---

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

[dmtrKovalenko]

I decided to delete this test that using NEXT_DATA global because it is diving too deep into next's internal implementation. Originally testing components with router usage should be a bad practice, but using more and more internal APIs is even worse because this test will fail for literally all users between next's releases

[elevatebart]

I have 2 non blocking comments.
LGTM