Provide a mechanism to filter using attribute data from a specific
commit (making use of `GIT_ATTR_CHECK_INCLUDE_COMMIT`).

Introduce `GIT_ATTR_CHECK_INCLUDE_COMMIT`, which like 4fd5748c allows
attribute information to be read from files in the repository.  4fd5748c
always reads the information from HEAD, while
`GIT_ATTR_CHECK_INCLUDE_COMMIT` allows users to provide the commit to
read the attributes from.

When looking up an attribute file in a commit, we can cache a
nonexistent attribute file indefinitely (since a commit could not
somehow later contain an attribute file).  Cache an empty buffer when an
attribute file does not exist in a given commit.

Allow filter users to provide an options structure instead of simply
flags.  This allows for future growth for filter options.

Filters use a short-lived structure to keep state during an operation to
allow for caching and avoid unnecessary reallocations.  This was
previously called the "filter options", despite the fact that they
contain no configurable options.  Rename them to a "filter session" in
keeping with an "attribute session", which more accurately describes
their use (and allows us to create "filter options" in the future).

Allow more advanced attribute queries using a `git_attr_options`, and
extended functions to use it.  Presently there is no additional
configuration in a `git_attr_options` beyond the flags, but this is for
future growth.

The attribute source object is now the type and the path.

We may want to extend the attribute source; use a structure instead of
an enum.

The enum `git_attr_file_source` is better suffixed with a `_t` since
it's a type-of source.  Similarly, its members should have a matching
name.

Optional stricter allocation checking (for `malloc(0)` cases)

Co-authored-by: lhchavez <lhchavez@lhchavez.com>

Add `GIT_DEBUG_STRICT_ALLOC` to help identify problematic callers of
allocation code that pass a `0` size to the allocators and then expect a
non-`NULL` return.

When given a 0-size allocation, `malloc` _may_ return either a `NULL`
_or_ a pointer that is not writeable.  Most systems return a non-`NULL`
pointer; AIX is an outlier.  We should be able to cope with this AIXy
behavior, so this adds an option to emulate it.

stdintification: use int64_t and INT64_C instead of long long

git__timer: Allow compilation on systems without CLOCK_MONOTONIC

For 32-bit int: There's no real reason for that ifdef if we explicitly
specify the stdint.h type.

For 64-bit int: ope, I made it signed accidentally

Makes usage of CLOCK_MONOTONIC conditional and makes functions that uses
git__timer handle clock resynchronization.

Call gettimeofday with tzp set to NULL as required by
https://pubs.opengroup.org/onlinepubs/9699919799/functions/gettimeofday.html

Make `FIND_PACKAGE(PythonInterp)` prefer `python3`

fix check for ignoring of negate rules

Fix wrong time_t used in function

config: fix included configs not refreshed more than once

This change makes it possible to prefer a python (version 3) interpreter
on systems where python2 and python3 coexist (where python2 is found as
`/usr/bin/python`).

Fix memory leak in git_smart__connect

git__timer: Limit ITimer usage to AmigaOS4

Passes w/ gcc 11 on Fedora x64.

Protip: So you don;t have to suffer,

```
perl -pe 's/(-?(?:0x)?[A-Fa-f0-9]+)([Uu])?[Ll][Ll]/\U$2INT64_C(\E$1)/mg'
```

Even on systems without C99 where long long and stdint are both
missing, we can shim stdint and point it to any compiler-specific
type (i.e long long, _int64, etc.).

Also next is constant suffixes and determining what needs to
include stdint.

This function doesn't interoperate with any system functions that
use the system time_t, but rather only works with the git_time_t
type in libgit2, which could be a different width than the system
one. Fixes a compile warning.

Consider files executable only if the user can execute them

Update from regex to pcre licensing information in docs/contributing.md

docs: fix some missing includes that cause Docurium to error out

Define WINHTTP_NO_CLIENT_CERT_CONTEXT if needed

docs: stop mentioning libgit2's "master" branch