Minor bug during update: list of dependent/blocking programs is a bit too broad

[Franzi]

Hi,

During a TortoiseGit self-update I got a prompt that the updater needed to
close a running process before it could continue, because it detected that
process as "using" TortoiseGit / Git.

The process in question was an unrelated CLI tool (claude.exe, an AI coding
assistant) that was simply invoking a separately installed Git for Windows
instance in a repository on my machine - it has no connection to TortoiseGit
itself and does not touch any files inside the TortoiseGit installation
directory.

As far as I can tell, TortoiseGit does not ship its own git.exe (there is
none in the TortoiseGit\bin folder), so I'd expect the updater's lock check
to only care about processes with open handles on TortoiseGit's own
binaries/DLLs (TortoiseGitProc.exe, TGitCache.exe, TortoiseGit*.dll, etc.),
not about arbitrary processes that happen to run git.exe from a separate
Git for Windows installation.

Is this expected/intended behavior, or is the lock check too broad here?

Versions:
- TortoiseGit: 2.19.1.0
- Git: git version 2.55.0.windows.2 (Git for Windows, C:\Program Files\Git)
- Windows: 11 Pro, build 10.0.26200 (x64)

Thanks!

Franz