Update error categories to match libgit2

I noticed that our client was returning some error messages that didn't make sense, turns out that libgit2 inserted a None = 0 error category and we did not update to reflect when we took that build.  Thus we were off by one!