fix: next 12.1.6 support and add tests

[ZachJW34]

• Closes UNIFY-1724

User facing changelog

n/a

Additional details

Adding tests for Next.js v12.1.6 since the testing support for component projects is much greater on 10.0-release. I've created a PR targeting master that has only the src changes so as to release this fix faster.

How has the user experience changed?

PR Tasks

• Have tests been added/updated?
• [na] Has the original issue (or this PR, if no issue exists) been tagged with a release in ZenHub? (user-facing changes only)
• [na] Has a PR for user-facing changes been opened in cypress-documentation?
• [na] Have API changes been updated in the type definitions?
• [na] 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

37428 • 0 • 454 • 0 • 5

---

Run details

Project	cypress
Status	Passed
Commit	ec66046
Started	May 17, 2022 10:16 PM
Ended	May 17, 2022 10:35 PM
Duration	18:52 💡
OS	Linux Debian - 10.11
Browser	Multiple

View run in Cypress Dashboard ➡️

---

Flakiness

	commands/net_stubbing.cy.ts		1
1	network stubbing > waiting and aliasing > can timeout waiting on a single response using "alias"
	commands/actions/click.cy.js		1
1	... > scroll-behavior > can scroll to and click elements in html with scroll-behavior: smooth
	e2e/origin/commands/assertions.cy.ts		1
1	cy.origin assertions > #consoleProps > .should() and .and()
	cypress/proxy-logging.cy.ts		2
1	Proxy Logging > request logging > xhr log has response body/status code when xhr response is logged second
2	Proxy Logging > request logging > xhr log has response body/status code when xhr response is logged second

---

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]

Why/how does this fix the problem? Do we know?

Also, CI seems to be failing - not sure if real problem or just needs a re-run.

Edit: you explained here: #21516. Seems fine. Not entirely sure how you figured this out or why this was changed in a patch release for Next.js.

[ZachJW34]

Going to merge when green, the corresponding PR to master has been merged and released.