Fix: Resolve git-lfs and husky hooks conflict in devcontainer setup

[aicodexp]

Problem

When starting the devcontainer, the setup fails due to a conflict between git-lfs and husky hooks:

Running the postCreateCommand from Feature 'ghcr.io/devcontainers/features/git-lfs:1'...
[16420 ms] Start: Run in container: /bin/sh -c /usr/local/share/pull-git-lfs-artifacts.sh
Fetching git lfs artifacts...
Hook already exists: pre-push
        #!/usr/bin/env sh
        . "$(dirname "$0")/h"
To resolve this, either:
  1: run `git lfs update --manual` for instructions on how to merge hooks.
  2: run `git lfs update --force` to overwrite your hook.
[16922 ms] postCreateCommand from Feature 'ghcr.io/devcontainers/features/git-lfs:1' failed with exit code 2.

Root Cause Analysis

The issue occurs because:

1. Husky runs first during npm install and sets core.hookspath to .husky/_
2. Git LFS feature runs later and attempts to install its hooks, but finds existing husky hooks
3. The conflict causes the devcontainer setup to fail

Note: Reversing the execution order wouldn't solve the problem either. If git-lfs ran first and modified .git/hooks, husky would later change core.hookspath to .husky/_, effectively bypassing the git-lfs hooks and leaving git-lfs silently improperly configured.

Current Hook Structure

• Husky creates hooks in .husky/_/ that source .husky/_/h
• The h script then calls any matching hook script in .husky/ if it exists
• Git LFS needs to inject its own hook logic into this chain

Solution

This PR implements a controlled merge of git-lfs hooks with husky's hook system:

1. Let husky complete its setup - maintains the existing hook infrastructure
2. Delay git-lfs hook installation - prevents the initial conflict
3. Merge hooks in postCreateCommand - combine git-lfs functionality with husky's hook chain

Implementation Details

The solution adds a custom script that:

• Extracts git-lfs hook content
• Merges it with husky's template structure
• Ensures both git-lfs and husky hooks execute correctly

Related Issues

• [typicode/husky#1431](Provide documentation for using Husky with git-lfs typicode/husky#1431) - Similar conflict reported
• [typicode/husky#1574](core.hooksPath is .husky/_, examples create hooks in .husky, prepare: husky overwrites anything .husky/_ typicode/husky#1574) - Discussion on core.hooksPath handling
• [microsoft/vscode-copilot-chat#88](Make devcontainer support for contributors work better out of the box #88) - Previous attempt to improve devcontainer support
• [typicode/husky#108](Git LFS and husky prepush hook? typicode/husky#108) - Git LFS and husky prepush hook compatibility
• [mastodon/mastodon#24884](Husky clobbers git hooks directory, causing systems with git-lfs installed to constantly install hooks mastodon/mastodon#24884) - Husky clobbering git hooks with git-lfs

[aicodexp]

@microsoft-github-policy-service agree