CMake: treat the ld flags as a list

These are treated as a list by CMake itself, which means that treating
them as a simple string can put semicolons in our ld command-line if we
have libraries which are not installed on the standard locations.

Treat the variable as a CMake list and replace it with the space-delimited
list just before writing it out to our pc file.

Plug a bunch of leaks

stash: test we apply using reflog-like indices

Fast builds?

We're installing dependencies via the APT addon now.

Fixes

Stash apply: stage new files even when not updating the index

Desenfuckenate prefix lookups

This reverts commit 969d4b70.

This was a fluke from Coverity. The length to all the APIs in the
library is supposed to be passed in as nibbles, not bytes. Passing it as
bytes would prevent us from parsing uneven-sized SHA1 strings.

Also, the rest of the library was still using nibbles (including
revparse and the odb_prefix APIs), so this change was seriously breaking
things in unexpected ways. ^^

pc: Put libcurl and libssh2 in Libs.private

Pass on to whoever wants to link to libgit2 statically the flags that we
would have used for these libraries.

Putting them in Requires.private as we do now makes pkg-config put their
dependencies in the linker arguments as well, which is not what we want.

Dont update index unnecessarily

When diffing the index with the workdir and GIT_DIFF_UPDATE_INDEX has been passed,
the previous implementation was always writing the index to disk even if it wasn't
modified.

Test that workdir diffs, when presented with UPDATE_INDEX, only
write the index when they actually make a change.

Rename FALLBACK to UNSPECIFIED

List `libcurl` in the generated `libgit2.pc`

Files that were new (staged additions) in the stash tree should
be staged when unstashing, even when not applying the index.

Provide `git_iterator_walk` to walk each iterator in lockstep,
returning each iterator's idea of the contents of the next path.

remote: insert refspecs with no rhs in FETCH_HEAD

Don't allow growing borrowed buffers

When a refspec contains no rhs and thus won't cause an explicit update,
we skip all the logic, but that means that we don't update FETCH_HEAD
with it, which is what the implicit rhs is.

Add another bit of logic which puts those remote heads in the list of
updates so we put them into FETCH_HEAD.

Fallback describes the mechanism, while unspecified explains what the
user is thinking.

This explains more closely what happens. While here, set an error
message.