test: set defaultBrowser to chrome

[MikeMcC399]

• partially addresses Respond to Electron deprecation in Cypress 16 #1883

Situation

Electron is used as the default browser throughout this repo.

With the release of Cypress 16.0.0 Electron has been deprecated:

Deprecated the Electron browser as a test browser. The Electron browser will be removed in a future major version of Cypress; switch to Chrome or another installed browser to avoid a breaking change when you upgrade. See Migrating away from the Electron browser.

Change

Chrome is the most used browser and is available in GitHub-hosted runners for each operating system, with the exception of ubuntu-24.04-arm, for which it has been requested through actions/runner-images#14567.

Use Firefox for ubuntu*-arm runner images.

For those examples that are not browser-specific, add the Browsers configuration setting defaultBrowsers: chrome.

Remove tests that explicitly specify electron.

This re-applies 68be0d4 from PR #1713.

---

Note

Low Risk
Changes are limited to example Cypress configs and workflow matrices; no runtime or security-sensitive application code is affected.

Overview
Prepares the repo for Cypress 16’s Electron browser deprecation by making Chrome the default test browser in example projects and tightening CI browser selection.

Example configs: Adds defaultBrowser: 'chrome' to the shared cypress.config.js files under examples/ (e2e, component, workspaces, etc.) so runs no longer rely on Electron when no browser is passed explicitly.

GitHub Actions: In example-basic.yml, both basic jobs pass a browser input of Firefox on ubuntu*-arm runners (where Chrome isn’t on the hosted image) and leave other OS matrix entries on the default. In example-docker.yml, Electron is dropped from the Docker browser matrix so container jobs only exercise Chrome, Edge, and Firefox (with existing arm64 Edge exclusion unchanged).

^{Reviewed by Cursor Bugbot for commit 963f971. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cypress-app-bot]

• 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.

[MikeMcC399]

@AtofStryker

Would you like to merge, since you've approved?