Launch WSL editors via CLI

[robertmonka]

🧢 Changes

• Launches VS Code-like editor URLs through the editor CLI when running inside WSL.
• Supports vscode, vscode-insiders, vscodium, cursor, windsurf, and trae URL schemes.
• Converts editor://file/... URLs into CLI arguments, including --goto for line/column targets.
• Preserves windowId=_blank behavior by passing --new-window.
• Percent-decodes file paths before launching the editor command.
• Falls back to the existing URL opener when not running in WSL, when the editor scheme is unsupported, or when the editor command is not available.
• Keeps the AppImage environment cleanup shared between GUI URL launching and CLI editor launching.
• Adds Linux-only unit tests for URL-to-editor-command conversion.

☕️ Reasoning

WSL does not reliably handle desktop editor URL schemes through the normal GUI opener path. For editors that also expose a command-line launcher, invoking the CLI directly is more predictable and lets GitButler open the requested file, line, column, and project window without relying on Windows-side URL association behavior.

The fallback path is intentionally unchanged for non-WSL Linux environments and unsupported editors, so existing URL opening behavior remains in place outside this specific case.

🧪 Testing

• Added Linux-only unit coverage for Cursor, VS Code new-window URLs, percent-decoded paths, and unsupported editor fallback.
• Not run locally while updating this PR description.

[Byron]

I'm very sorry, but I have to close all of your PRs on the basis of them being fully automated coming from a profile that doesn't show much related history.

Thanks a lot for your understanding.

[robertmonka]

Hi Byron, thanks for the explanation. I understand the concern.

These PRs were created with AI-agent assistance, and I should have made that clearer. For this one specifically, I verified the behavior in practice in a WSL setup, understand the functional intent of the change, and I’m responsible for following up on any issues or requested adjustments.

To reduce review burden, would you be open to reconsidering just this focused WSL bugfix first?

The intent here is narrow: make editor launching from WSL go through the CLI path so configured editors can open correctly from that environment.

I’m happy to resubmit it with a shorter, more conventional PR description, add or adjust tests if needed, and avoid opening more PRs until we agree on the expected contribution process.