Re: [PATCH v3 17/17] fsck: report invalid object type-path combinations

Improve the error that's emitted in cases where we find a loose object
we parse, but which isn't at the location we expect it to be.

I'll hold off reviewing this for 2 reasons - firstly, I don't think it's
related to the other patches that are about reporting a wrong object
type, and secondly, in the case of repository corruption, I don't see
how useful computing (and reporting) the hash of a corrupt object is.

If someone else wants to take a look at this, that would be great, but
otherwise I would suggest splitting this into its own patch set.