feat: add support for chrome for testing browser

[mschile]

• Closes Chrome for Testing - we can't run your tests #28554
• Closes Google Chrome for testing - version not parsed correctly #28123

Additional details

• Added Google Chrome for Testing as a new known browser: --browser chrome-for-testing
  • Has a display name of Chrome for Testing
  • For auto-detection:
    • On Mac, is assumed to be at /Applications/Google Chrome for Testing.app
    • On Linux, looks for the chrome binary on the PATH
    • On Windows, looks for the executable here: C:/Program Files (x86)/Google/Chrome for Testing/chrome.exe
• Renamed the display name for Google Chrome Canary, from Canary to Chrome Canary
• Renamed appId to bundleId since it is a reference to the CFBundleIdentifier
• Passed --disable-infobars to ensure the toolbars are removed. This caused the screenshot sizes to go back to what they were before.

Steps to test

• Download Google Chrome for Testing
• Place the application in the correct location
• Verify Cypress shows the browser in the browser selection page
• Verify passing --browser chrome-for-testing uses the correct browser
• Place the application in a non-standard location and verify passing the browser path loads the browser correctly (e.g. --browser /path/to/browser)
• Verify both Chrome and Chrome for Testing show up separately and can be used independently

How has the user experience changed?

PR Tasks

• Have tests been added/updated?
• Has a PR for user-facing changes been opened in cypress-documentation? docs: add chrome for testing browser cypress-documentation#6038
• [n/a] Have API changes been updated in the type definitions?

[cypress]

cypress    Run #58928

Run Properties:   Passed #58928  •  5d87c4bd1a: updating svg

Project	cypress
Branch Review	mschile/chrome_for_testing
Run status	Passed #58928
Run duration	16m 40s
Commit	5d87c4bd1a: updating svg
Committer	Matthew Schile
View all properties for this run ↗︎

---

Test results
Failures	0
Flaky	2
Pending	26
Skipped	0
Passing	770
View all changes introduced in this branch ↗︎

UI Coverage  66.27%
Untested elements	26
Tested elements	55

Accessibility  96.2%
Failed rules	0 critical   4 serious   1 moderate   0 minor
Failed elements	200

[jennifer-shehane]

It worked fine for me. A few comments

[cypress-bot]

Released in 13.17.0.

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