…S Protocol

Signed-off-by: Derrick Stolee <[email protected]>

This is a fix for a performance regression introduced by #822. That
change updated the packfile installation process to call a different
packfile installation method after some upstream changes to the packfile
data structures.

However, while I thought I read the new packfile methods as including a
modification of the MRU cache, it apparently does not fully install the
packfile in the list.

This manifests in something like `git checkout` where the missing blobs
are queued for download, downloaded in blob packfiles, and then the
checkout process continues. During the process of writing the data to
the worktree, the "updating files" progress indicator slows to a crawl
because it was "missing" the blobs and then downloaded them on-demand.

This fixes the issue by being less fancy about packfiles and using
`packfile_store_reprepare()` to just reset the full packfile list. This
is more future-proof and isn't very expensive compared to the packfile
download.

I augmented a test to include tracing that shows a necessary blob is
queued for packfile download and is not later downloaded via an
immediate request. Without the code change, that test would fail.

* [X] This change only applies to interactions with Azure DevOps and the
GVFS Protocol.

build-git-installers: prepare for the big split of mingw-w64-git

In git-for-windows/MINGW-packages#172, the
`mingw-w64-git` package was split into multiple packages, with the
new primary package as Git for Windows is concerned being the
`mingw-w64-git-for-windows-addons` one.

Accommodate for that change by simply adding (almost) all of the packages
that were built to the command-line via `--pkg` options, instead of
hardcoding the `mingw-w64-git` and `mingw-w64-git-doc-html` one.

Signed-off-by: Johannes Schindelin <[email protected]>