feat(desktop): support Microsoft Edge as a selectable Browser Bridge browser on macOS

## Summary

OpenCLIApp on macOS is Chrome-first: it detects and opens Google Chrome, but does not detect or let users select Microsoft Edge. This prevents an Edge-only user from completing the browser-extension setup and makes the desktop App appear incompatible with Edge.

## Environment

- macOS (Apple Silicon)
- OpenCLIApp 0.1.36
- OpenCLI CLI / daemon 1.8.5
- Microsoft Edge 150.0.4078.83
- OpenCLI extension 1.0.22

## Actual behavior

The desktop App probes Google Chrome installation paths only:

```text
/Applications/Google Chrome.app
/Applications/Google Chrome Beta.app
/Applications/Google Chrome Canary.app
```

There is no equivalent Microsoft Edge detection and no browser-selection preference. App actions related to the browser/extension therefore default to Chrome; changing the macOS default browser does not select Edge.

The daemon itself can accept the Edge Chromium-extension connection: `opencli doctor` reports the extension conncted, and `opencli profile list` shows a conncted context. The limitation appears to be in the desktop App UI / browser-launch and detection layer, not the bridge protocol.

## Steps to reproduce

1. Install OpenCLIApp on macOS.
2. Install and enable the OpenCLI extension in Microsoft Edge, without using Google Chrome.
3. Open OpenCLIApp and use the browser/extension setup action or inspect its browser status.
4. Observe that the App looks for or opens Google Chrome, with no Edge option.

## Expected behavior

- Detect Microsoft Edge at `/Applications/Microsoft Edge.app` on macOS.
- Offer a browser preference (Chrome, Edge, or another supported Chromium browser), or use the browser whose OpenCLI extension is currently conncted.
- Use the selected browser for extension setup/help links and status reporting.
- Rename Chrome-specific UI copy where appropriate to Chromium browser / Browser Bridge.

## Workaround

Manually open `edge://extensions`, install/enable OpenCLI in Edge, and use the CLI bridge. This works at the daemon level, but the desktop App still remains Chrome-first.

Start from the desktop App's macOS browser detection and browser/extension setup action, using the listed Chrome application paths as the reference point. Trace how browser status, launch behavior, setup/help links, and UI copy are selected; done means Edge is detected, selectable or selected from its connected extension, and Chrome-specific wording is updated where appropriate.

Written by the indexing model from the issue text.