Fix Windows CI: skip bash-path-incompatible test on win32

[Copilot]

All Windows CI test jobs were failing with 1 test out of 1050 — the detect-project writes project metadata to the registry and project directory test in tests/hooks/hooks.test.js.

Root cause

The test builds a bash shell command string by embedding path.join()-generated paths directly:

const shellCommand = [
  `cd "${repoDir}"`,                          // e.g. C:\Users\...\repo on Windows
  `source "${detectProjectPath}" >/dev/null`, // backslashes → bash escape sequences
  'printf "%s\\n" "$PROJECT_ID"',
  'printf "%s\\n" "$PROJECT_DIR"'
].join('; ');

const proc = spawn('bash', ['-lc', shellCommand], { ... });

On Windows, path.join() returns backslash-separated paths. Inside a bash command string, \r, \U, etc. are interpreted as escape sequences — cd silently fails, source never runs, and no project.json is written.

Fix

Add a process.platform === 'win32' early-return guard, matching the existing pattern for other bash-script tests in this file:

if (process.platform === 'win32') {
  console.log('    (skipped — bash script paths are not Windows-compatible)');
  return true;
}

detect-project.sh is a Unix bash script; testing its execution on Windows via embedded shell command strings is not meaningful.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[Copilot]

Pull request overview

This PR fixes failing Windows CI by skipping a bash-path-sensitive hook test on win32, aligning with other platform-conditional tests in the hooks test suite.

Changes:

• Add a Windows-only early return to skip the detect-project writes project metadata... test when running on win32.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The skip guard returns true, but asyncTest() ignores the callback’s return value (it only awaits it). For consistency with other skips in this file (which just return;) and to avoid implying the return value is meaningful, consider using return; here as well.

Suggested change

	return true;
	return;