Handle repository workingDir with other remote Before this change, it the URL from the GitVersionConrolSpec might not have matched the remote of the workingDir repository, and a pull command would have been executed. But, the caller's intent would not have been followed.
Test and cover some more cases Specifically: * Can clone into an empty working directory that already exists. * Cannot populate a non-reposioty working directory with a file in it. * Cannot populate a non-reposioty working directory, even with a `.git` subdirectory.