GVFS.Payload: drop VS code-analysis marker files from payload

Visual Studio's MSBuild for native C++ projects emits a
<binary>.exe.lastcodeanalysissucceeded marker file next to each
produced executable to record that PREfast / code analysis ran
successfully on it. Those marker files are pure build-time
bookkeeping with no runtime purpose, but the GVFS.Payload layout
step xcopies the entire native bin\x64\<Config>\ folder for each
of GitHooksLoader, GVFS.PostIndexChangedHook, GVFS.ReadObjectHook
and GVFS.VirtualFileSystemHook -- so the markers end up in the
Payload, get packaged into SetupGVFS.exe, and finally land on
end-user machines as e.g. GitHooksLoader.exe.lastcodeanalysissucceeded
in 'C:\Program Files\VFS for Git\'.

Extend the existing layout.bat cleanup block (which already strips
*.runtimeconfig.json, *.deps.json, and orphaned managed PDBs) to
also recursively delete *.lastcodeanalysissucceeded from the
output directory so they're never shipped.

Signed-off-by: Matthew John Cheetham <mjcheetham@outlook.com>

Author: mjcheetham

GVFS/GVFS.Payload/layout.bat

@@ -59,6 +59,8 @@ RMDIR /S /Q %OUTPUT%\x86
 REM Remove stray managed artifacts (AOT binaries don't need these)
 DEL /Q %OUTPUT%\*.runtimeconfig.json 2>nul
 DEL /Q %OUTPUT%\*.deps.json 2>nul
+REM Remove VS C++ code-analysis marker files generated next to native exes
+DEL /S /Q %OUTPUT%\*.lastcodeanalysissucceeded 2>nul
 REM Remove orphaned managed PDBs (these libraries are compiled into AOT exes)
 DEL /Q %OUTPUT%\GVFS.Common.pdb 2>nul
 DEL /Q %OUTPUT%\GVFS.Platform.Windows.pdb 2>nul