feat: Node version schema update

[mjhenkes]

• Closes Have default nodeVersion be set to system instead of bundled #18684

User facing changelog

This is a follow-up PR to #18732 where I missed updating the cypress.schema.json file with the updated values. This PR should have the same change log as the previous PR.

Thanks for spotting this @emilyrohrbough !

Additional details

How has the user experience changed?

This change will not impact user experience.

PR Tasks

• Have new configuration options been added to the cypress.schema.json? <-- whoops, I apparently missed this step on the last pr.

[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.

[jennifer-shehane]

Shouldn't this have 'system' as the default?

This description should be reversed also since the logic would apply if set to 'bundled'.

Suggested change

	"description": "If set to 'system', Cypress will use the node version that was used to launch the cli when executing your plugins. Otherwise, Cypress will use the Node version bundled with Cypress."
	"description": "If set to 'bundled', Cypress will use the Node version bundled with Cypress. Otherwise, Cypress will use the Node version that was used to launch the Cypress. This Node version is used when executing your plugins file and building spec files."

[mjhenkes]

Technically there is no default now because adding either system or bundled will trigger the deprecation warning.

https://github.com/cypress-io/cypress/blob/9.0-release/packages/server/lib/config_options.ts#L153-L155

I'm not sure exactly how to use this file, but I didn't want to encourage people to add the 'nodeVersion' option to config.

[mjhenkes]

Actually should I remove the nodeVersion entry entirely because it's deprecated?

[jennifer-shehane]

But the deprecation warning is just a warning - the value still works. I don't understand the blocker for showing the default value as it is in the schema.

[jennifer-shehane]

If things are deprecated they are still documented as before because the value is still completely functional, it just warns that it will be removed later.

[mjhenkes]

We met in standup and decided to restore the default and mark the option as deprecated in the description.

[cypress]

---

Test summary

18577 • 3 • 214 • 7 • 0

---

Run details

Project	cypress
Status	Failed
Commit	1943211
Started	Nov 5, 2021 4:01 PM
Ended	Nov 5, 2021 4:12 PM
Duration	11:09 💡
OS	Linux Debian - 10.9
Browser	Multiple

View run in Cypress Dashboard ➡️

---

Failures

Run group: 5x-driver-electron (Linux, Electron )
	net_stubbing_spec.ts		1
1	network stubbing > waiting and aliasing > can timeout waiting on a single request using "alias.request"
Run group: 5x-driver-firefox (Linux, Firefox )
	xhr_spec.js		1
1	... > no status when request isnt forced 404
Run group: 5x-driver-chrome:beta (Linux, Chrome beta )
	net_stubbing_spec.ts		1
1	network stubbing > waiting and aliasing > can timeout waiting on a single request using "alias.request"

---

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