feat: Replace static contributor JSON with dynamic GitHub API fetch

[SakshamSinghal20]

What kind of change does this PR introduce?

Feature Enhancement - This PR introduces a feature enhancement to the Community page data loading mechanism by fetching contributor data dynamically from the GitHub API at build time instead of relying on a hard-coded JSON file.

Issue Number:

• Closes ✨ Enhancement: Fetch Community contributors dynamically via GitHub API at build time #2099
• Related to: N/A
• Others?: N/A

Screenshots/videos:

Not applicable, as this change affects data sourcing and not visual layout. The Community page UI will look the same, but with an up-to-date list of contributors fetched dynamically from the GitHub API.

If relevant, did you update the documentation?

Not required for this change, as the behavior of the Community page remains the same from a user's perspective and the enhancement is internal to the build-time data sourcing logic.

Summary

This PR updates the Community page so that contributor data is fetched from the GitHub API at build time using getStaticProps, instead of being read from the static community-users.json file. The GitHub API response is normalized to match the existing community-users.json structure and assigned to the same variable currently consumed by the UI (for example, imageData), allowing the existing rendering, filtering, and shuffling logic to work unchanged. This ensures that the contributor list remains accurate and up to date over time, reduces manual maintenance, and minimizes the overall code changes needed.

Does this PR introduce a breaking change?

No, this PR does not introduce a breaking change. The Community page continues to receive data in the same shape that it previously read from community-users.json, and all existing UI behavior is preserved; only the source of the data has changed to a build-time GitHub API fetch.

Checklist

Please ensure the following tasks are completed before submitting this pull request.

• Read, understood, and followed the contributing guidelines.

[github-actions]

Hi @SakshamSinghal20! Thanks a lot for your contribution!

I noticed that the following required information is missing or incomplete: kind of change description

Please update the PR description to include this information. You can find placeholders in the PR template for these items.

Thanks a lot!

[github-actions]

Hi @SakshamSinghal20! Thanks a lot for your contribution!

I noticed that the following required information is missing or incomplete: kind of change description

Please update the PR description to include this information. You can find placeholders in the PR template for these items.

Thanks a lot!

[github-actions]

built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

Name	Status	Preview	Last Commit
website	✅ Ready (View Log)	Visit Preview	5854eb1

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (2c94143) to head (5854eb1).
⚠️ Report is 7 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main     #2101   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           30        30           
  Lines          633       633           
  Branches       196       196           
=========================================
  Hits           633       633           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 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.