chore: add finos/git-proxy to the project list

[jescalada]

What this changes

Adds finos/git-proxy to the project list. Plenty of other popular FINOS projects are already in the list, and GitProxy already makes use of OSSF scorecard (currently with a score of 8.7). The problem is that LFX Insights fetches the score based on the weekly cron job rather than the API, thus GitProxy appears unindexed:

Related

How it was tested

Checklist

• Commits are signed off (git commit -s)
• make build and make test pass
• make lint is clean
• Specs/docs updated if behavior changed
• No employer/internal references added

If this PR touches the batch pipeline (cron/):

• If cron/internal/format changed, the corresponding engine change exists
  upstream and schema_gen_test.go passes

If this PR touches the scan inventories (cron/internal/data/*.csv):

• make add-projects was run and its output committed
• make validate-projects passes

[jescalada]

Just finished verifying that all checks (make build, make test, make lint and make validate-projects) are passing.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 49.49%. Comparing base (e435c38) to head (40289ae).
⚠️ Report is 257 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #140      +/-   ##
==========================================
+ Coverage   42.71%   49.49%   +6.78%     
==========================================
  Files          48       60      +12     
  Lines        2568     3291     +723     
==========================================
+ Hits         1097     1629     +532     
- Misses       1383     1504     +121     
- Partials       88      158      +70     

Components	Coverage Δ
api	59.70% <57.70%> (∅)
cron	33.48% <82.51%> (+6.44%)	⬆️
core	68.55% <ø> (ø)

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[justaugustus]

@jescalada — Thanks for the submission and the additional context on LFX Insights!

[jescalada]

@justaugustus Thanks for the quick review! 🙂