The 32-bit ARM QEMU builds are flaky when running `lstat`. Disable those
testing `lstat`'s `st_size` temporarily.

diff: don't stat empty file on arm32 (flaky test)

sha256: support dynamically loaded openssl

fetch: support OID refspec without dst

Our CI test infrastructure virtualizes arm32 in docker, which is a
sometimes imperfect situation. In `diff::workdir::can_diff_empty_file`,
avoid the stat to ensure that the file is zero bytes; there is an odd
issue running in qemu when emulating arm32 that we should skip.

SHA256: add a SHA256 implementation backend

gcc (mingw) warns when you cast the result of `GetProcAddress`; cast the
results to `void *` before casting them to the actual result.

When GIT_SHA1_WIN32 or GIT_SHA256_WIN32 is used, ensure that we test
both CryptoNG ("cng") and CryptoAPI.

Adding SHA256 support prompted an overdue refactoring of some of the
unnecessary complexity around the CNG/CryptoAPI abstraction.

Add support for a SHA256 hash algorithm, and add the "builtin" SHA256
hash engine (from RFC 6234).

The more generic GIT_ERROR_SHA allows for SHA256 errors as well as SHA1.

Eliminate the `sha1` folder, move it down into `hash` so that future
impelmentations can share common code.

Remove the "generic" implementation; it should never be used; it only
existed for a no-dependencies configuration, and our bundled sha1dc
satisfies that requirement _and_ is correct.

Benchmarking suite

Support the ability to create a refspec that is a single object ID
without a destination.

clone: update bitbucket tests

Fix a string concatenation bug when validating extensions

As builtin extensions are evaluated in the latter half of `check_valid_extension`, a string `cfg` is concatenated with the static string 'extension.' and the value from `builtin_extension`, before being compared with the configured value. This string is not being cleared while iterating through the names of the extensions. Because there is currently only one extension ('noop'), the bug was never noticible.

This patch corrects the behavior by clearing the string on each iteration, as is done in the first block.

Some minor fixes for issues discovered by coverity

cmake: export libraries needed to compile against libgit2

Add a benchmark test suite that wraps hyperfine and is suitable for
producing data about test runs of a CLI or A/B testing CLIs.

Allow for options in the `cmake --build` phase, so that callers can
specify (eg) the config type.

Rename our build setup scripts to include the `build` name so that we
can add additional CI setup scripts with no ambiguity.

If users are using us as a direct dependency (via `add_subdirectory`)
then they may want to know the libraries to link to; tell them.

Mistakenly `&&` when we should have `||`d.

When we encounter a situation where we need to exit, simply `return -1`
instead of trying to set `len = -1` and then jumping to the exit
handler, which would erroneously do work based on the `len` value.

If we're safely asserting (and returning an error to the caller), we
should still unlock our mutex.

Now that we safely assert and return, we may need to be in a place where
we need to unlock mutexes or cleanup resources.  Provide
`ASSERT_WITH_CLEANUP` that permits for this behavior by taking a block.

CLI (redux)

Introduce a simple command that emulates `git hash-object`.