fix: No longer display tags on stderr data in component testing

[cacieprins]

• Closes webpack info logs less readable with CYPRESS.STDERR annotations - re-open #32569 #32769

Additional details

When Cypress intentionally writes to stderr, it tags the content so that it will be preserved and written to the top level stderr. The @packages/stderr-filtering package takes care of tagging data and filtering the tags (and untagged data) from the stderr stream. This prevents benign stderr messages from Electron from surfacing.

In component testing run mode with webpack 5, the out stream was getting tagged. Unfortunately, that entrypoint to the binary was not captured by the filtering part of @packages/stderr-filtering.

This moves filter streaming from @packages/electron to the spawn logic in @packages/cli, ensuring it wraps the outermost process and filters any tags that come through stderr.

Steps to test

1. yarn binary-build (choose: overwrite)
2. yarn binary-package [--skipSigning, if on osx]
3. With the fresh binary, run component testing in the webpack5/react project in cypress-component-testing-apps: https://github.com/cypress-io/cypress-component-testing-apps/tree/main/react-webpack5-js
4. Confirm there is no CYPRESS.STDERR tags in the output stream

How has the user experience changed?

PR Tasks

• Have tests been added/updated?
• [NA] Has a PR for user-facing changes been opened in cypress-documentation?
• [NA] Have API changes been updated in the type definitions?

[cypress]

cypress    Run #69130

Run Properties:   Failed #69130  •  94db40ee6b: add stderr-filtering back to electron/open for system tests

Project	cypress
Branch Review	fix/ct-stderr-tags-in-prod
Run status	Failed #69130
Run duration	19m 13s
Commit	94db40ee6b: add stderr-filtering back to electron/open for system tests
Committer	Cacie Prins
View all properties for this run ↗︎

---

Test results
Failures	2
Flaky	9
Pending	1112
Skipped	0
Passing	27174
View all changes introduced in this branch ↗︎

UI Coverage  62.34%
Untested elements	27
Tested elements	48

Accessibility  98.98%
Failed rules	0 critical   3 serious   1 moderate   0 minor
Failed elements	18

---

Tests for review

  src/debug/DebugSpec.cy.tsx • 1 failed test • app-ct

View Output

Test		Artifacts
An uncaught error was detected outside of a test		Test Replay

  cypress/e2e/runner/reporter.command_errors.cy.ts • 1 failed test • app-e2e

View Output

Test		Artifacts
errors ui > assertion failures with new sourcemap root		Test Replay Screenshots

  e2e/origin/config_env_expose.cy.ts • 1 flaky test • 5x-driver-electron

View Output

Test		Artifacts
cy.origin- Cypress.config() > serializable > overwrites different values in secondary if one exists in the primary		Test Replay

  issues/28527.cy.ts • 1 flaky test • 5x-driver-electron

View Output

Test		Artifacts
issue 28527 > fails and then retries and verifies about:blank is not displayed		Test Replay Screenshots

  issues/28527.cy.ts • 1 flaky test • 5x-driver-chrome:beta

View Output

Test		Artifacts
issue 28527 > fails and then retries and verifies about:blank is not displayed		Test Replay Screenshots

  commands/net_stubbing.cy.ts • 1 flaky test • 5x-driver-firefox

View Output

Test		Artifacts
... > stops waiting when an xhr request is canceled		</td> </tr></table>   commands/files.cy.js • 1 flaky test • 5x-driver-firefox View Output Test Artifacts src/cy/commands/files > #readFile > retries to read when ENOENT </td> </tr></table> The first 5 flaky specs are shown, see all 9 specs in Cypress Cloud.