[vcpkg_from_git] Add --skip-repo to git lfs install

[helmesjo]

git lfs install --local --force was installing hooks (that are AFAICT unnecessary for a headless build fetch, nothing is ever pushed) into the temp clone. This in turn fails when core.hooksPath points to an existing dir/symlink. In particular, having git lfs install touch user configurations can be considered quite intrusive.

Specifically, from the docs:

Perform the following actions to ensure that Git LFS is setup properly:

* Set up the clean and smudge filters under the name "lfs" in the global
Git config.
* Install a pre-push hook to run git-lfs-pre-push(1) for the current
repository, if run from inside one. If "core.hooksPath" is configured in
any Git configuration (and supported, i.e., the installed Git version is
at least 2.9.0), then the pre-push hook will be installed to that
directory instead.

From git lfs install -h:

--skip-repo:
  Skips installation of hooks into the local repository; use if you want to
  install the LFS filters but not make changes to the hooks.  It is valid to use
  --local, --global, or --system in conjunction with this option.

Example error:

     │ File: C:\Users\<user>\<project>\.vcpkg\buildtrees\<dependency-w-lfs>\git-lfs-install-x64-windows-static-md-err.log
─────┼──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
   1 │ mkdir C:\Users\<user>\.githooks: Cannot create a file when that file already exists.
   2 │ To resolve this, either:
   3 │   1: run `git lfs update --manual` for instructions on how to merge hooks.
   4 │   2: run `git lfs update --force` to overwrite your hook.

[BillyONeal]

Thanks!

[BillyONeal]

Looks like there are build failures. Some are baseline issues that are fixed in these:

• Baseline fixes for 2026-04-10. #51099
• [icey] Devendor nlohmann-json. #51086
• [trieste] Do not take generic artifact names #51049

but some are not.

Build failures need to be investigated.

[helmesjo]

Looks like there are build failures. Some are baseline issues that are fixed in these:

• Baseline fixes for 2026-04-10. #51099
• [icey] Devendor nlohmann-json. #51086
• [trieste] Do not take generic artifact names #51049

but some are not.

AFAICT none of the failures (and ports) use/invoke COMMAND "${GIT}" lfs install --local --force --skip-repo (at least not directly), and all of them seem to be FILE_CONFLICTS (that seem to be solved by the PRs you referenced). Was there any of them in particular that you could point me towards?

[BillyONeal]

Hmmmm I think I got confused by how Azure DevOps and GitHub are connected to each other; the "checks" tab listed a whole lot more failures. Pushed a merge with those baseline fixes to see if that fixes it.

[helmesjo]

Sigh... What caused the full rebuild? Should I not have clicked "ready for reaview"? :)
FYI the previous builds all passed.

[BillyONeal]

Thanks!