feat: webpack 5 support

[dmtrKovalenko]

• Closes Webpack 5 support #8900

User facing changelog

Overall changing is related to webpack v5 for instance error messages were changed from

Webpack Compilation Error
.<path>/_test-output/imports_nonexistent_file_spec.js
Module not found: Error: Can't resolve './does/not-exist' in '<path>/_test-output'
Looked for and couldn't find the file at the following paths:
[<path>/_test-output/does/not-exist]
[<path>/_test-output/does/not-exist.wasm]
[<path>/_test-output/does/not-exist.mjs]
[<path>/_test-output/does/not-exist.js]
[<path>/_test-output/does/not-exist.json]
 @ .<path>/_test-output/imports_nonexistent_file_spec.js 1:0-26
`

To the more readable

exports['webpack preprocessor - e2e has less verbose syntax error 1'] = `
Webpack Compilation Error
.<path>/_test-output/syntax_error_spec.js
Module build failed (from /[root]/node_modules/babel-loader/lib/index.js):
SyntaxError: <path>/_test-output/syntax_error_spec.js: Unexpected token (1:18)

�[0m�[31m�[1m>�[22m�[39m�[90m 1 | �[39mdescribe(�[32m'fail'�[39m�[33m,�[39m �[33m-�[39m�[33m>�[39m)�[0m
�[0m �[90m   | �[39m                  �[31m�[1m^�[22m�[39m�[0m
�[0m �[90m 2 | �[39m�[0m

Make sure that [0m�[31m�[1m symbols are used to render the code snippet preview when the error appeared

Additional details

This PR proves that @cypress/webpack-preprocessor works nicely with the v5 version of webpack. It also removes the outdated and deleted compiler.plugin API usage.

How has the user experience changed?

PR Tasks

• Have tests been added/updated?
• Has the original issue or this PR been tagged with a release in ZenHub?
• Has a PR for user-facing changes been opened in cypress-documentation?
• Have API changes been updated in the type definitions?
• Have new configuration options been added to the cypress.schema.json?

[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

8701 • 0 • 118 • 3 • 1

---

Run details

Project	cypress
Status	Passed
Commit	77d07fb
Started	Nov 9, 2020 6:23 PM
Ended	Nov 9, 2020 6:36 PM
Duration	12:34 💡
OS	Linux Debian - 10.2
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]

The reason for CI failures is that create-react-app aka react-scripts does not support webpack v5 facebook/create-react-app#9510

[JessicaSachs]

@dmtrKovalenko there's some failing examples that seem real -- the webpack configuration API has changed. Can you look into it?

[jennifer-shehane]

Unfortunately we have to close this PR due to inactivity. Please open a new PR addressing the original issue and any requested changes.