Auto install git-theta when doing a track as people often forget this step

[blester125]

related to #229

[craffel]

Hmm, for some reason I was thinking you'd fail out or warn or prompt the user rather than just doing a transparent install. I'd be a bit worried about this being a hidden side-effect, but I defer to you.

[blester125]

Hmm, for some reason I was thinking you'd fail out or warn or prompt the user rather than just doing a transparent install. I'd be a bit worried about this being a hidden side-effect, but I defer to you.

That is what I was planning to do, but I realized there are like 5 different possible places where the configuration for git-theta could be stored. We don't currently support setting it any place but ~/.gitconfig so I figured we would want to support setting it in those places in addition to checking them. So this solution seems to be a good stop-gap for a new user creating a new repo until we support the finer-grained settings.

I'm going to now close this issue and instead list it as an enhancement and expand on where to check for files and what not and link it in a new (enhancement) issue about supporting finer grained config files.

[blester125]

Updated, now checking if git theta is installed will check all possible locations for an install (based on the git config --list command. So we don't need to worry about how they installed it so we don't have to run a global install each time.

[blester125]

closes #229