retry on HTTP 50X Error when calling Chef REST API
read http_retry_count from chef config in the spec; add HTTP error code in the log.
Deprecate CookbookVersion#latest_cookbooks
Alias #latest_cookbooks.
Work around breaking change in git

In git 1.7.10 shallow clone behavior was changed from shallow cloning
all branches by default, to only shallow cloning the branch being
checked out. Unfortunately, this breaks prior and expected behavior in
Chef as, on subsequent deploys it is not possible to switch branch,
because no other branches exist in the cache-copy of the repo.

To fix this we must use the `--no-single-branch` flag when performing
the inital clone. Unfortunately this flag is not supported by git
versions prior to 1.7.10, so we must check the version of git before
deciding if the workaround is required.

It probably makes sense to make this prior behavior optional in a future
patch, however this one just seeks to give consistent results across all
versions of git.
Merge pull request #2141 from opscode/mcquin/Issue-2090

Deprecate CookbookVersion#latest_cookbooks
Merge pull request #1912 from jessehu/CHEF-ISSUE-1904

retry on HTTP 50X Error when calling Chef REST API
add changelog for 50x errors
Merge pull request #2156 from opscode/lcg/50x-errors-changelog

add changelog for 50x errors
Merge pull request #2148 from mal/issue/1563

Work around breaking change in git clone