Use SHA256 for file checksums. SHA1 makes no sense as a default in 2023.

Given that we're just looking at a file checksum to see if it's changed,
this does not need to take repository's OID type into account or
otherwise be configurable.

Looks like a double-free here.

Teach the smart transport more about oid types, instead of assuming SHA1.

The opt mechanism isn't _really_ meant to be for feature flags, and it's
weird to feature flag shallow / unshallow at all.

sha256: less hardcoded SHA1 types and lengths

xdiff: move xdiff to 'deps'

meta: the main branch is now v1.7.0

config: return `GIT_ENOTFOUND` for missing programdata

When the programdata path is missing, ensure that we pass down the
`GIT_ENOTFOUND` error to the caller instead of converting it to a
generic `-1`.

The config file checksum is only used to detect changes internally -- it
is not stored within the repository. Therefore this need not be
configurable.

Use SHA256 everywhere, regardless of the repository object format.