Test with some postimages that actually grow/shrink from the
original, adding new lines or removing them.  (Also do so without
context to ensure that we can add/remove from a non-zero part of
the line vector.)

Parse values up to and including `\377` (`0xff`) when unquoting.
Print octal values as an unsigned char when quoting, lest `printf`
think we're talking about negatives.

`oid_strlen` has meant one more than the length of the string.
This is mighty confusing.  Make it mean only the string length!
Whomsoever needs to allocate a buffer to hold a string can null
terminate it like normal.

Handle prefixes (in terms of number of path components) for patch
parsing.

When a text file is added or deleted, use the file names from the
`diff --git` header instead of the `---` or `+++` lines.  This is
for compatibility with git.

We may have parsed binary data, set the `SHOW_BINARY` flag which
indicates that we have actually computed a binary diff.

Now that `git_diff_delta` data can be produced by reading patch
file data, which may have an abbreviated oid, allow consumers to
know that the id is abbreviated.

No need to replicate the old_file/new_file members, or plumb them
strangely up.

Patches can now come from a variety of sources - either internally
generated (from diffing two commits) or as the results of parsing
some external data.

When we are provided some input buffer (with a length) to inflate,
and it contains more data than simply the deflated data, fail.
zlib will helpfully tell us when it is done reading (via Z_STREAM_END),
so if there is data leftover in the input buffer, fail lest we
continually try to inflate it.

Handle the application of binary patches.  Include tests that
produce a binary patch (an in-memory `git_patch` object),
then enusre that the patch applies correctly.

Introduce `git_zstream_inflatebuf` for simple uses.

Refactor the git_delta functions to have consistent naming and
parameters with the rest of the library.