fix: avoid nextjs unsafeCache and watchOptions

[elevatebart]

• Closes UNIFY-1133

In webpack 5 it seems that loaders called with the exact same query are not re-run.
This creates a situation where the Cypress file watcher is updating the files but the new files are never pushed in the loader. It results in Cypress throwing a (No tests found) error since the spec exists but not in the AUT.

In this PR I disable caching and unsafe caching for the browser.js file.

[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

19278 • 0 • 218 • 0 • 5

---

Run details

Project	cypress
Status	Passed
Commit	8e451b1
Started	Mar 3, 2022 7:06 PM
Ended	Mar 3, 2022 7:18 PM
Duration	11:46 💡
OS	Linux Debian - 10.10
Browser	Multiple

View run in Cypress Dashboard ➡️

---

Flakiness

	commands/net_stubbing_spec.ts		2
1	network stubbing > waiting and aliasing > can timeout waiting on a single request using "alias.request"
2	network stubbing > waiting and aliasing > can timeout waiting on a single request using "alias.request"
	settings_spec.js		1
1	Settings > file preference panel > loads preferred editor, available editors and shows spinner
	cypress/proxy-logging_spec.ts		2
1	... > works with forceNetworkError
2	Proxy Logging > request logging > xhr log has response body/status code

---

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]

1. Any perf implication?
2. CI is failing hardcore - did this cause that?
3. Gonna need to add a test for this somehow - it's not even clear how to test by hand, but we definitely need some kind of automated testing here.

As for the actual implementation, cool hack, no idea if there's a better/cleaner way (likely, but I don't know what it is).

@BlueWinds is working around webpack lately, they may be interested to see this PR/issue.

[ZachJW34]

Can you add some information on how you tested this? I pulled it down and I wasn't able to get a new spec detected. When I cleared the next webpack cache, I started receiving this error:

Also, this seems to be a next issue, not a webpack 5 issue. Both cra-5 and vue-cli-5 (which uses webpack 5) doesn't have this problem, so I wonder if we should dig into what the Next webpack config is doing that causes this refresh issue rather than make a change to the @cypress/webpack-dev-server.

[ZachJW34]

I don't think there is any good way to test this. We could probably write a unit test where we spin up a dev-server with a Next webpack config, touch a file and assert that webpack recompiles but we would need to have Next v12 installed. I would take note of this since our testing is lacking in this area

[ZachJW34]

We need to remove the optional chaining as this will fail on node v12