feat: Enable requiring cy.origin dependencies with require() and import()

[chrisbreiding]

• Closes Remove need for Cypress.require and support dynamic import #24293

User facing changelog

• Enabled using dependencies within the cy.origin() callback using require() and dynamic import(). Removed Cypress.require().

Additional details

Steps to test

How has the user experience changed?

PR Tasks

• Have tests been added/updated?
• Has the original issue (or this PR, if no issue exists) been tagged with a release in ZenHub? (user-facing changes only)
• Has a PR for user-facing changes been opened in cypress-documentation?
• Have API changes been updated in the type definitions?

[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

45918 • 0 • 4490 • 0 • 5

---

Run details

Project	cypress
Status	Passed
Commit	3aecb02
Started	Oct 18, 2022 8:20 PM
Ended	Oct 18, 2022 8:37 PM
Duration	16:55 💡
OS	Linux Debian - 11.4
Browser	Multiple

View run in Cypress Dashboard ➡️

---

Flakiness

	migration.cy.ts		1
1	Full migration flow for each project > migration-e2e-component-default-test-files > skips the file renaming
	commands/assertions.cy.js		2
1	... > has a pending state while retrying for commands with onFail
2	... > has a pending state while retrying for commands with onFail
	commands/xhr.cy.js		1
1	src/cy/commands/xhr > abort > aborts xhrs currently in flight
	specs_list_latest_runs.cy.ts		1
1	App/Cloud Integration - Latest runs and Average duration > when no runs are recorded > shows placeholders for all visible specs

---

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

[mschile]

Suggest specifying the required version of the webpack preprocessor.

[chrisbreiding]

The trouble is, I won't know what version that is until this is merged and it's actually released.

Also, when this was originally released, I could have guessed the version was going to be 5.13.0 and hard-coded that into the error message, but webpack-preprocessor@5.13.0 ended being broken. That required a 5.13.1 release, meaning the error message would have been misleading. I think recommending the latest version is the safest bet.