[Feature]: Support ghq for cloning repositories (or at least a ghq-style destination path) #24893

Problem

I manage all my local repositories with ghq, so every checkout lives at $(ghq root)/<host>/<owner>/<repo> (e.g. ~/ghq/github.com/owner/repo). When I add a project by cloning in T3 Code, I have to pick the destination by hand each time, and the result ends up outside my ghq tree unless I navigate there and create the <host>/<owner> folders myself. Other tools (and my scripts) then can't find the repo where they expect it.

This hurts most from the mobile app. A common flow for me is: I'm away from my desk, find an unfamiliar repository, and want T3 Code to clone it on my Mac and dig into it. Picking a sensible destination folder from a phone is fiddly, so these exploratory clones end up scattered in random places and I have to clean them up later. If clones automatically landed in my ghq tree, they would be organised with zero effort.

Proposal

Ideally, an option to clone with ghq itself:

• A setting like "Clone with ghq" that runs ghq get <url> (respecting the user's ghq config, e.g. ghq.root, SSH vs HTTPS) and adds the resulting path as the project.

At minimum, a ghq-style destination path:

• A clone destination mode that places the repo at <root>/<host>/<owner>/<repo>, where <root> defaults to ghq root (or git config ghq.root) when ghq is installed, and is configurable otherwise.
• Missing <host>/<owner> directories are created automatically.
• Applies to clones started from the mobile app too, so no destination picking is needed there.

Why

ghq's layout is common among developers who juggle many repositories, and it's also what tooling like ghq list / fzf pickers rely on. Matching it would make cloned projects land exactly where existing workflows expect, with no manual folder picking.

Related

• [Bug]: Swift iOS app ignores "Add project starts in" and always browses from ~/ #16507 ("Add project starts in" setting)