Fix Coverity builds (#5672)

As of three months ago, Git for Windows' [Coverity builds
fail](https://github.com/git-for-windows/git/actions/workflows/coverity.yml?query=branch%3Amain).

The reason is most likely the most recent release, 2025.3. Its [release
notes](https://documentation.blackduck.com/bundle/coverity-docs/page/webhelp-files/relnotes_latest.html)
do not shed any light into the issue (and does not mention that they
bundle JDK20 and JDK22 in addition to JRE, because what's better than a
single Java installation: three, right?).

My investigation turned up `.dll` files that are located in Coverity's
`bin/` directory which have the same name as `.dll` files in Git for
Windows' SDK. As a consequence, the former override the latter and throw
off MSYS2's logic to find the MSYS2 root directory given the location of
certain `.dll` files.

This PR fixes this issue, and while at it, enhances the Coverity
workflow to print out the build log in case of failure.

Author: dscho

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,64 @@
+ - [ ] I was not able to find an [open](https://github.com/git-for-windows/git/issues?q=is%3Aopen) or [closed](https://github.com/git-for-windows/git/issues?q=is%3Aclosed) issue matching what I'm seeing
+
+### Setup
+
+ - Which version of Git for Windows are you using? Is it 32-bit or 64-bit?
+
+```
+$ git --version --build-options
+
+** insert your machine's response here **
+```
+
+ - Which version of Windows are you running? Vista, 7, 8, 10? Is it 32-bit or 64-bit?
+
+```
+$ cmd.exe /c ver
+
+** insert your machine's response here **
+```
+
+ - What options did you set as part of the installation? Or did you choose the
+   defaults?
+
+```
+# One of the following:
+> type "C:\Program Files\Git\etc\install-options.txt"
+> type "C:\Program Files (x86)\Git\etc\install-options.txt"
+> type "%USERPROFILE%\AppData\Local\Programs\Git\etc\install-options.txt"
+> type "$env:USERPROFILE\AppData\Local\Programs\Git\etc\install-options.txt"
+$ cat /etc/install-options.txt
+
+** insert your machine's response here **
+```
+
+ - Any other interesting things about your environment that might be related
+   to the issue you're seeing?
+
+** insert your response here **
+
+### Details
+
+ - Which terminal/shell are you running Git from? e.g Bash/CMD/PowerShell/other
+
+** insert your response here **
+
+ - What commands did you run to trigger this issue? If you can provide a
+   [Minimal, Complete, and Verifiable example](http://stackoverflow.com/help/mcve)
+   this will help us understand the issue.
+
+```
+** insert your commands here **
+```
+ - What did you expect to occur after running these commands?
+
+** insert here **
+
+ - What actually happened instead?
+
+** insert here **
+
+ - If the problem was occurring with a specific repository, can you provide the
+   URL to that repository to help us with testing?
+
+** insert URL here **

Documentation/technical/api-path-walk.adoc

@@ -79,3 +79,4 @@ See example usages in:
 	`t/helper/test-path-walk.c`,
 	`builtin/pack-objects.c`,
 	`builtin/backfill.c`
+	`builtin/pack-objects.c`

builtin/pack-objects.c

@@ -4672,7 +4672,7 @@ static void get_object_list(struct rev_info *revs, int ac, const char **av)
 
 	warn_on_object_refname_ambiguity = save_warning;
 
-	if (use_bitmap_index && !get_object_list_from_bitmap(revs))
+	if (use_bitmap_index && !path_walk && !get_object_list_from_bitmap(revs))
 		return;
 
 	if (use_delta_islands)

ci/run-build-and-tests.sh

@@ -26,6 +26,7 @@ linux-TEST-vars)
 	export GIT_TEST_NO_WRITE_REV_INDEX=1
 	export GIT_TEST_CHECKOUT_WORKERS=2
 	export GIT_TEST_PACK_USE_BITMAP_BOUNDARY_TRAVERSAL=1
+	export GIT_TEST_PACK_PATH_WALK=1
 	;;
 linux-clang)
 	export GIT_TEST_DEFAULT_HASH=sha1

preload-index.c

@@ -22,6 +22,8 @@
 
 static struct fscache *fscache;
 
+static struct fscache *fscache;
+
 /*
  * Mostly randomly chosen maximum thread counts: we
  * cap the parallelism to 20 threads, and we want

t/t7406-submodule-update.sh

@@ -1103,6 +1103,7 @@ test_expect_success 'submodule update --quiet passes quietness to fetch with a s
 	git clone super4 super5 &&
 	(cd super5 &&
 	 # This test var can mess with the stderr output checked in this test.
+	 GIT_TEST_PACK_PATH_WALK=0 \
 	 GIT_TEST_NAME_HASH_VERSION=1 \
 	 GIT_TEST_PACK_PATH_WALK=0 \
 		git submodule update --quiet --init --depth=1 submodule3 >out 2>err &&