fix: bump resource class for tests that require node_modules install

[ZachJW34]

Details

npm-webpack-preprocessor and npm-webpack-dev-server were flaky on CI. These tests both require a yarn install which was causing the agent to run out of memory. This PR bumps the resource_class for both of these tests to medium

Before:
https://app.circleci.com/pipelines/github/cypress-io/cypress/27313/workflows/48943cd1-1381-42ef-b5c3-93a50b68f424/jobs/1031151/steps

After:
https://app.circleci.com/pipelines/github/cypress-io/cypress/27315/workflows/ebc15162-ae83-430f-97d8-add2ac352620/jobs/1031282

[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

18699 • 0 • 204 • 0 • 4

---

Run details

Project	cypress
Status	Passed
Commit	41eb6a1
Started	Nov 24, 2021 3:21 PM
Ended	Nov 24, 2021 3:33 PM
Duration	12:08 💡
OS	Linux Debian - 10.10
Browser	Multiple

View run in Cypress Dashboard ➡️

---

Flakiness

	commands/net_stubbing_spec.ts		3
1	network stubbing > intercepting request > should delay the same amount on every response
2	network stubbing > waiting and aliasing > can timeout waiting on a single request using "alias.request"
3	network stubbing > waiting and aliasing > can timeout incrementally waiting on requests
	settings_spec.js		1
1	Settings > file preference panel > loads preferred editor, available editors and shows spinner

---

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

[marktnoonan]

It'll be really nice to not have to rerun these for this reason 🎉

[lmiller1990]

Will leave merging this one to @flotwig

[flotwig]

In a perfect world, we wouldn't be doing any yarn install outside of the root node_modules_install. It's just for the example projects that we need it for these 2 jobs, right?

If so, I think that when #18574 merges we can go ahead and convert these tests that have dependencies to use system-tests instead, and maybe even drop these circle jobs altogether. Is there an issue or task created for this yet? Created an issue to track converting these to system-tests: #19088

[ZachJW34]

@flotwig Though these tests aren't for testing examples, I believe they can still be converted to system tests. They were installing different deps so as to rerun the unit tests against them (for example, Webpack 4 vs Webpack 5), but having two different system tests (one to cover each dep we support) will suffice.