fix(git-hooks): prefer core.hooksPath and avoid symlink on Windows

[Shiven0504]

Summary

git-hooks/install-hooks.sh unconditionally removes ../.git/hooks and attempts to create a symlink to ../git-hooks/hooks. On Windows (and some restricted environments) creating symlinks requires elevated privileges or is unsupported, and the script can unintentionally remove existing hooks. This causes the installer to fail or damage developer setups.

Steps to reproduce

1. On a Windows machine without symlink privileges, run from repo root:

bash git-hooks/install-hooks.sh

2. Observe that ln -s fails (or that .git/hooks was removed), and that hooks are not installed.

Expected behavior

• Installer should set up hooks in a cross-platform way without requiring symlink privileges and without deleting existing hooks unless explicitly requested.

My Proposed fix

• Use git config core.hooksPath git-hooks/hooks by default (works cross-platform and avoids symlinks).
• Only attempt a symlink as a fallback when git is not available, and show a clear warning.
• Only run rustup component add rustfmt if rustup is installed.

Patch / PR

I have a proposed patch that updates git-hooks/install-hooks.sh to prefer git config core.hooksPath and to guard rustup usage. The patch is ready in a branch fix/git-hooks-installer.