midx: do not verify the checksum on load

Include test results data in CI

midx: fix large offset table check.

Add link to Tcl bindings for libgit2

chore(docs): Add Pharo to language bindings

Though both are correct, this makes it clear that we're dealing with
the same value.

It's insufficient to only check if the offset high order bit is set, we
must also check to see if object_large_offsets are in use.

This bug is causing objects to appear missing because they can't be
found in the index.

Avoid mismatches between the container uid/gid and the actions runner,
build the container with the actions runner's uid/gid

This is something we only want to do during explicit verification rather than on
every load.

Verifying does not seem like a big deal when we're running with test workloads
but once your `multi-pack-index` reaches gigabytes, we spend more time hashing
this than doing any work.

The dates we use in `refs::revparse::date` has just passed the ten years, so
now everything is beyond ten years, leading to an unexpected commit being
returned.

Adjust it to 11 years so it all looks fine again.

cli: clone

Fix missing include

remote: Delete a now-inexistent API declaration

Now that the containers all set the user id of the libgit2 build user to
the user id of the host runner, we can write to a shared build output
volume.

CentOS 8 is no longer supported; use CentOS stream.

Use the runner's uid/gid for the containers for sanity when sharing
files across volumes.

sha256: refactoring in preparation for sha256

6fc6eeb6 replaced the remote options
with `git_remote_connect_options`. The function definitions were
removed, but one function declaration remained, causing linker errors if
one tried to use it.

This change removes the declaration of
`git_transport_smart_proxy_option` to better reflect reality.

Provide a mechanism to add a signal handler for Unix or Win32.

Provide a class that will display progress information to the console.
Initially, it contains callbacks for fetch progress and checkout
progress.

Validate repository directory ownership

Introduce the `GIT_OPT_SET_OWNER_VALIDATION` option, so that users can
disable repository ownership validation.

Obey the `safe.directory` configuration variable if it is set in the
global or system configuration. (Do not try to load this from the
repository configuration - to avoid malicious repositories that then
mark themselves as safe.)

Pull the global configuration loader out of the symlink check so that it
can be re-used.

Test that we prevent opening directories that are not owned by
ourselves.

Provide a mock for file ownership for testability.

Ensure that the repository directory is owned by the current user; this
prevents us from opening configuration files that may have been created
by an attacker.

Provide individual file ownership checks for both the current user and
the system user, as well as a combined current user and system user
check.

The indexer expects raw oid data, provide it.

A multi-pack index uses raw oid data, use a byte array to index
into them.

The index contains entries with raw oid data, use a byte array for the
raw entry data.

A packfile contains arrays of raw oid data, use a byte array to index
into them.