chore: remove rawJson from Cypress.state()

[emilyrohrbough]

• Closes Remove rawJson from stored Cypress state #23945

develop/packages/driver/src/cypress.ts#L222

Check the config value received when Cypress starts and you'll see we are storing the rawJson with the value & resolved.from values in Cypress.state().

We collect this date for presenting the config resolution in the App, but the driver doesn't need/use this info.

• 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

40224 • 0 • 3354 • 0 • 1

---

Run details

Project	cypress
Status	Passed
Commit	6d3e2ad
Started	Oct 12, 2022 2:13 PM
Ended	Oct 12, 2022 2:29 PM
Duration	15:33 💡
OS	Linux Debian - 11.3
Browser	Multiple

View run in Cypress Dashboard ➡️

---

Flakiness

	cypress/e2e/e2e/origin/config_env.cy.ts		1
1	cy.origin- Cypress.config() > serializable > overwrites different values in secondary if one exists in the primary

---

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]

Since this is not part of the public API (undocumented) I don't know if we need to mark it as BREAKING, do we? BREAKING is usually for public API changes (I understand this might technically break someone, though, but it's equally weird to see a deprecation in a major that was never an official feature to begin with).

[emilyrohrbough]

yeah, I can go either way, but would rather we just push it out in 11.0 just in case.