Handle Relative Git Worktree Paths in Worktree Detection

[Copilot]

Worktree auto-detection handled absolute gitdir entries but failed when .git/worktrees/*/gitdir contained relative paths (e.g. from git worktree add --relative-paths). This change normalizes both formats so relative-path worktrees are discovered consistently.

• Path normalization in git worktree parsing

  • Added parseGitWorktreePath(gitdirPath, gitdirContent) in extensions/git/src/git.ts.
  • Resolves relative gitdir entries against the gitdir file directory.
  • Normalizes separators and strips trailing .git (and nested suffix) for stable worktree root paths.

• Detection flow update

  • Replaced inline string replacement logic in getWorktreesFS() with the new parser.
  • Removes implicit assumption that gitdir content is always absolute and POSIX-shaped.

• Focused regression coverage

  • Added unit tests in extensions/git/src/test/git.test.ts for:
    • relative gitdir paths
    • absolute gitdir paths

const worktreeGitPath = path.isAbsolute(gitdirContent)
	? gitdirContent
	: path.resolve(path.dirname(gitdirPath), gitdirContent);

return worktreeGitPath.replace(/[\\/]\.git(?:[\\/].*)?$/, '');

[Otto-Deviant1904]

LGTM