Add warning for `--load-extension` usage with Chrome 137+ branded builds

[AtofStryker]

Summary

Starting with Chrome 137, official Chrome branded builds will remove support for the --load-extension command line switch. Cypress should warn users when this combination is detected to help them migrate to supported alternatives.

Implementation Details

Add a warning when the following conditions are met:

• Chrome version 137 or higher is detected
• It's a branded build (not Chrome For Testing/Chromium)
• The --load-extension argument is present
• Running in headed mode

Documentation on https://docs.cypress.io should be updated to include that extension loading does not working in chrome branded 137+

The warning should inform users that:

1. Chrome 137+ branded builds do not support the --load-extension argument
2. Alternative browsers that support --load-extension:
   • Chrome For Testing
   • Chromium
   • Other Chrome variants

Example Warning Message

Warning: Chrome 137+ (branded) does not support the --load-extension argument. 
To test with extensions, please use Chrome For Testing, Chromium, or another Chrome variant that supports loading unpacked extensions.

References

• Chrome Release Schedule
• Chromium RFC Discussion
• Related issue: Update @cypress/puppeteer plugin to warn users about Chrome 137+ branded builds #31703
• Related issue: Provide alternative to --load-extension flag in Chrome #31690

[alexsch01]

Cypress currently uses --load-extension by default

I guess when this gets implemented on Cypress' side, it won't be using the --load-extension argument anymore

[AtofStryker]

Cypress currently uses --load-extension by default

I guess when this gets implemented on Cypress' side, it won't be using the --load-extension argument anymore

@alexsch01 There currently aren't plans to change how --load-extension works. The goal right now is to warn if Chrome branded is being used with the --load-extension argument to inform users that this will no work with Chrome branded 137+ and Chrome for Testing or another Chrome variant must be used

[alexsch01]

@AtofStryker right but Cypress currently includes this argument by default in both run and open modes
do you mean that a future Cypress version will emit a warning just because it's launched in Chrome branded?

[AtofStryker]

@AtofStryker right but Cypress currently includes this argument by default in both run and open modes do you mean that a future Cypress version will emit a warning just because it's launched in Chrome branded?

@alexsch01 correct for Chrome 137+ since we are unable to load the extension

[jennifer-shehane]

@alexsch01 Only if you are explicitly loading an extension or loading cypress/puppeteer as one of our features. There will be no change to the functionality of Cypress outside of that.