Separate dev and release userData paths

[danipen]

Summary

A dev run (bun run dev) and an installed release shared GitGrove's identity, so they landed on the same userData directory — and thus the same single-instance lock (Chromium keeps that lock file inside userData). This made the two mutually exclusive: launching dev while the release was open (or vice versa) just routed argv into the running instance and quit silently.

This change gives the dev build its own userData directory (… (dev)) so its lock and state stand alone:

• Release and dev now run side by side.
• Dev never clobbers your real recents / session state.

The override runs before requestSingleInstanceLock and before the app ready event, as required.

Test plan

• Launch an installed release, then bun run dev — both windows open independently.
• Confirm dev no longer overwrites the release's recent-repos / window-state.