fix: Handle SSH over HTTPS GitHub remote URLs

[charlesvien]

Problem

GitHub URL parsing relied on hand-rolled regex that missed SSH-over-HTTPS forms and didn't handle nullable input.

Changes

1. Parse GitHub URLs with git-url-parse instead of regex
2. Expose path on parseGitHubUrl and reuse it for parsePrUrl
3. Accept nullable input on both parsers and validate scheme/owner
4. Drop the duplicate extractRepoKey helper in folders service
5. Use parsed.path directly in git service compare and PR list calls
6. Add edge case tests for SSH, HTTPS and PR URL variants

How did you test this?

Manually

Publish to changelog?

[charlesvien]

• feat: Resolve issues and PRs by full GitHub URL #2094
• feat: Track individual subscription start and cancel events #2079
• fix: Handle SSH over HTTPS GitHub remote URLs #2049 👈 (View in Graphite)
• feat: Polish onboarding, tour and branch checkout flows #2047
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[greptile-apps]

Prompt To Fix All With AI

Fix the following 1 code review issue. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 1
packages/git/src/utils.test.ts:71-85
**Identical org and repo values hide swap bugs**

Every successful-parse test case uses `"posthog"` for both `organization` and `repository`. If `segments[0]` and `segments[1]` (or `scpMatch[2]` and `scpMatch[3]`) were ever transposed, all tests would still pass. Using distinct values like `"my-org"` / `"my-repo"` in at least one test per code path would catch that class of regression. This violates the simplicity rule "expresses every idea that we need to express."

_{Reviews (1): Last reviewed commit: "Handle SSH over HTTPS GitHub remote URLs" | Re-trigger Greptile}

[k11kirky]

woof, i expect there is some libs to handle this, but fine for now.