[ci]: make priority:develop:sync worktree-safe for unattended runs

[svelderrainruiz]

Summary

Fix priority:develop:sync so it works from linked worktrees and remains safe for unattended runs.

Problem

tools/priority/Sync-OriginUpstreamDevelop.ps1 currently builds its lock path under repoRoot/.git, which is a file in linked worktrees. That causes lock acquisition to self-time out and forces manual sync fallbacks after PR merges.

Acceptance Criteria

• priority:develop:sync -- --fork-remote origin succeeds from both the root checkout and a linked worktree.
• Sync locks use the common git dir so serialization remains repo-wide across worktrees.
• The default writer-lease root uses the common git dir.
• Develop sync diagnostics/reporting include resolved git admin paths (gitDir, gitCommonDir, lockPath).
• Regression coverage reproduces the linked-worktree failure mode and verifies the fixed behavior.

Notes

• Scope is limited to the unattended hot path, not a repo-wide .git cleanup.
• This issue exists to make post-merge fork sync deterministic for unattended delivery.

[svelderrainruiz]

Implemented on branch issue/origin-11-worktree-safe-develop-sync.

PR:

• Make priority:develop:sync worktree-safe for unattended runs compare-vi-cli-action#1024

Validated locally:

• node --test tools/priority/__tests__/develop-sync.test.mjs tools/priority/__tests__/agent-writer-lease.test.mjs
• node tools/npm/run-script.mjs priority:develop:sync -- --fork-remote origin

The sync helper now resolves git-dir / git-common-dir, uses a repo-wide lock path that is safe from linked worktrees, records those admin paths in the report, and can fall back from the broken SSH push URL to the HTTPS fetch URL on this host.

[svelderrainruiz]

Implemented upstream via PR LabVIEW-Community-CI-CD#1024 and merged into develop.