failed clone leaves dangling directory

[rcoup]

Describe the bug

If you clone a repo, Kart creates a directory for it. If the clone fails before any transfer starts, the empty repo directory is left behind. This can happen if the repo path/URL is wrong, or the user doesn't authenticate.

To Reproduce

$ kart clone me@github.com:wiz/foo
Cloning into '/Users/rcoup/code/kart-data/foo/.clone'...
me@github.com: Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
Error: Error calling git clone
$ ls -l foo
total 0

$ # compare with git clone:
$ git clone me@github.com:wiz/foo
Cloning into 'foo'...
me@github.com: Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
$ ls -l foo
ls: cannot access 'foo': No such file or directory

Expected behaviour

If Kart creates the directory, then it should delete it again if the clone never starts transferring.

**Version Info **

• OS: macOS 14.3
• Version: v0.15.0