fix: error regression - unexpected ANSI color chars shown on Firefox warning message about chromeWebSecurity

[davidmunechika]

• Closes Unexpected chars shown on Firefox warning message about chromeWebSecurity #20496

User facing changelog

Fix regression that caused ANSI color chars to show up on Firefox warning message about chromeWebSecurity

Additional details

This regression was introduced in Cypress version 9.5.0 as a result of this PR: #20072 where errors originating from the server (@packages/errors) were altered as part of a larger errors improvement.

To fix this regression, I simply stripped the ANSI chars from the warning message, since this config will display differently in 10.0 and will be deprecated with multi-domain anyway.

How has the user experience changed?

Before:

After:

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)
• [n/a] Has a PR for user-facing changes been opened in cypress-documentation?
• [n/a] Have API changes been updated in the type definitions?
• [n/a] 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

19278 • 0 • 218 • 0 • 0

---

Run details

Project	cypress
Status	Passed
Commit	53fd890
Started	Mar 7, 2022 5:23 PM
Ended	Mar 7, 2022 5:35 PM
Duration	12:00 💡
OS	Linux Debian - 10.10
Browser	Multiple

View run in Cypress Dashboard ➡️

---

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

[cypress-bot]

Released in 9.5.2.

This comment thread has been locked. If you are still experiencing this issue after upgrading to
Cypress v9.5.2, please open a new issue.