fix: plugin for next 11.0.2 moved webpack-config

[elevatebart]

• Closes Cypress tests fail #17519, Component testing broken on next@11.0.2-canary.20 #17476

User facing changelog

A change in NextJs 11.0.2-canary.20's internal structure of next made cypress plugin error with a file not found. This fixes it.

[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

18192 • 0 • 214 • 7 • 1

---

Run details

Project	cypress
Status	Passed
Commit	8be901d
Started	Jul 31, 2021 3:51 AM
Ended	Jul 31, 2021 4:02 AM
Duration	10:59 💡
OS	Linux Debian - 10.8
Browser	Multiple

View run in Cypress Dashboard ➡️

---

Flakiness

	cypress/integration/commands/net_stubbing_spec.ts		1
1	network stubbing > intercepting request > can intercept utf-8 request bodies without crashing

---

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

[lmiller1990]

How did you test? Just creating a new project?

We need to find a better strategy. I think this should be a separate module where the version is the same as the Next.js version that it works with. Like how ts-jest matches vue-jest.