Fix goal progress verification

[Rohith31-WD]

Summary

• Reject client-supplied progress updates for GitHub-synced goals (commits and prs)
• Keep manual progress updates available for non-GitHub goals
• Add regression tests for synced-goal PATCH behavior

Root cause

The PATCH endpoint validated that current was numeric and within target bounds, but it trusted the client as the source of truth for goals whose progress should come from GitHub activity.

Validation

• npm exec -- tsc --noEmit
• npm exec -- vitest run test/goals-patch-progress.test.ts could not start in this sandbox because the local runner's esbuild subprocess was blocked with spawn EPERM.

Fixes Priyanshu-byte-coder#1753

[github-actions]

GSSoC Label Checklist 🏷️

@Rohith31-WD — please apply the appropriate labels before merging:

Difficulty (pick one):

• level:beginner — 20 pts
• level:intermediate — 35 pts
• level:advanced — 55 pts
• level:critical — 80 pts

Quality (optional):

• quality:clean — ×1.2 multiplier
• quality:exceptional — ×1.5 multiplier

Validation (required to score):

• gssoc:approved — counts for points
• gssoc:invalid / gssoc:spam / gssoc:ai-slop — does not score

Type labels (type:*) are auto-detected from files and title. Review and adjust if needed.
Points formula: (difficulty × quality_multiplier) + type_bonus

[github-actions]

🎉 Merged! Thanks for contributing to DevTrack.

If the project has been useful to you, a ⭐ star on the repo is the easiest way to support it — it helps DevTrack get discovered by more developers.

Keep an eye on open issues for your next contribution!