config: provide an "origin" for config entries

README.md: Fix link to conan packages

Revert "CMake: Search for ssh2 instead of libssh2."

proxy: Return an error for invalid proxy URLs instead of crashing.

Test proxies specified by both host:port format in configuration
options, environment variables, and `http.proxy` configuration.

The common format for specifying proxy URLs is just 'host:port'. Handle
the common case.

Introduce a url parser that defaults to treating poorly specified URLs
as http URLs. For example: `localhost:8080` is treated as
`http://localhost:8080/` by the http-biased url parsing, instead of a
URL with a scheme `localhost` and a path of `8080`..

Refactor url parsing to simplify the state-passing (introducing a
struct) and add a path parser for future reusability.

ssh: fix known_hosts leak in _git_ssh_setup_conn

stransport: macOS: replace errSSLNetworkTimeout, with hard-coded value

- Constant only available in 10.13+, causing build failures for older macOS releases
Fixes: https://github.com/libgit2/libgit2/issues/6606

fix: Add missing include for oidarray.

Add a missing include for `git2/oidarray.h` so build doesn't fail on
using `git_oidarray` when using custom transports.

Fixes #6607

Provide two memory-backed configuration backends -- one that takes a
string in config file format `[section] key=value` and one that takes a
list of strings in `section.key=value` format.

A git_config_entry now knows the type of the origin for the entry
("file", "memory", etc) and the path details (for files, the path on
disk). This is propagated through snapshots.

The opaque `payload` on an entry is unnecessary and distracting; config
entries should follow the patterns of other objects and use space
elsewhere in the structure with a "base" config entry struct embedded.

Don't set entry data when we "get" an entry from the collection, add the
data to the entry before it's put into the collection. This keeps the
entry creation logic in a single place.

repository: make cleanup safe for re-use with grafts

We are allowed to call `git_repository__cleanup` multiple times, and this
happens e.g. in rugged if we want to free up resources before GC gets around to
them.

This means that we cannot leave dangling pointers in it, which we were doing
with the grafts. Fix this by setting the pointers to NULL after freeing the resources.

meta: update version numbers to v1.8

v1.7: release Kleine Raupe Nimmersatt

deps: update pcre to 8.45

#6576 git_diff_index_to_workdir reverse now loads untracked content

tests: add allocator with limited number of bytes

Fixes #6344: git_branch_move now renames the reflog instead of deleting.