Co-authored-by: Edward Thomson <ethomson@github.com>

CLI: progress updates

refs: fix missing error message

docs: fix couple of typos

revparse: Remove error-prone, redundant test

midx: do not verify the checksum on load

Avoid too much flashing on the console with updates about throughput.
Only update throughput once a second.

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

Originally introduced in: 776a6a8e

This test case has recently been fixed in bdab2238, but that fix will only last for a year. Next year the same problem will crop up and the test will need to be re-edited.

This is not ideal as
- This test case becomes an unnecessary burden for developers
- Downstream distros or even just users who want to build older versions of libgit2 are guaranteed to have this test fail

Furthermore, this test case is entirely unnecessary, as the functionality that was originally (see 776a6a8e) intended to be tested is well-covered by subsequent tests which specify a date instead of a "x ago" specification.

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 removed
`git_transport_smart_proxy_option`, and there was nothing added to
replace it. That made it hard for custom transports / smart
subtransports to know what remote connect options to use (e.g. proxy
options).

This change introduces `git_transport_smart_remote_connect_options` to
replace it.

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.