Connect: add e2e tests for app configuration

[gzdunek]

Adds tests for the Configuration section of the test plan:

teleport/.github/ISSUE_TEMPLATE/webtestplan.md

Lines 1154 to 1169 in e9bcb1a

	- Configuration
	- [ ] Verify that clicking on More Options icon `⋮` > Open Config File opens the `app_config.json` file in your editor.
	- Verify that this works on:
	- [ ] macOS
	- [ ] Windows
	- [ ] Linux
	- Change a config property and restart the app. Verify that the change has been applied.
	- [ ] Change a keyboard shortcut.
	- [ ] Change `terminal.fontFamily`.
	- Provide the same keyboard shortcut for two actions.
	- [ ] Verify that a notification is displayed saying that a duplicate shortcut was found.
	- Provide an invalid value for some property (for example, set `"keymap.tab1": "ABC"`).
	- [ ] Verify that a notification is displayed saying that the property has an invalid value.
	- Make a syntax error in the file (for example, set `"keymap.tab1": not a string`).
	- [ ] Verify that a notification is displayed saying that the config file was not loaded correctly.
	- [ ] Verify that your config changes were not overridden.

I renamed app to electronApp to avoid names like app.app (now it's app.electronApp).
I also enabled customizing the config file in tests.

Manual Test Plan

My laptop.

Test Cases

• The new tests are passing.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 000261f643

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Restore usage-consent handling in launchApp

launchApp now returns immediately after domcontentloaded and no longer dismisses the first-run "Anonymous usage data" modal. This changes the behavior for existing callers outside the fixture path (for example e2e/scripts/open-connect.ts, which still calls launchApp(dataDir.path) directly), so on a fresh CONNECT_DATA_DIR the modal can block login() from clicking "Connect" and make the helper script fail/hang. Please keep launchApp robust for fresh profiles (or make all callers seed usageReporting.enabled=false before launching).

Useful? React with 👍 / 👎.

[ravicious]

I added the same setting in my other upcoming PR with tests. But since we're turning it off, I also have a separate test which explicitly removes this from the config and tests that the telemetry dialog is shown on the first launch. I'll try to rebase my stuff over your changes.