streamline layout and enhance community social proof

[IanoNjuguna]

The purpose of this PR is to make the Community Section more engaging.

Related to #218

Type of Change

Check the type of change this PR introduces:

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Refactor (improves code structure or readability without changing functionality)
• Other (please describe):

Changes Made

1. Created a new Contributors.tsx component that dynamically fetches and displays real-time contributor data from the GitHub API.
2. Implemented a filtering system in the contributors list to automatically exclude automated bot accounts and Dependabot.
3. Integrated the Contributors component into the CommunitySection layout between the description paragraph and action buttons.
4. Updated the section heading and description copy to focus on community assistance and suggesting improvements.
5. Added the all-time repository pulse on the right half of the section.

Checklist

Ensure you have completed the following steps before submitting your PR:

• My code follows the project's coding style and guidelines.
• I have performed a self-review of my own code.
• I have commented my code, particularly in hard-to-understand areas.
• I have updated the documentation (if applicable).
• My changes generate no new warnings or errors.
• I have added tests that prove my fix is effective or that my feature works.
• I have checked for merge conflicts.
• I have rebased my branch onto the latest main or master branch.

[HarunJr]

Thanks for putting this together. The visual design and the use of live data look fantastic!
I have a few architectural notes to help us polish this up before merging:

1. Lockfiles (website/bun.lock & website/yarn.lock) It looks like bun was used locally. This project strictly uses yarn, so committing bun.lock could cause confusion for other contributors and break our CI.

• Suggestion: Please delete bun.lock, run yarn install to cleanly restore yarn.lock, and update the PR.

I have highlighted some Rate limit issues and some nick picks before. other than that I have a few nit picks on the UI design.

1. For consistency and visual pull poposes purposes, kindly restore the rounded joint intersect to the original orange rounded corner and center it since you have removed the other Visit GitHub Repository from this location.

The goal is for this to be the primary button visitors want to click on, so it should be a different colot i.e: Orange for Prominence.

2. As the Scondary button, again, we can maintain the rounded corners but consider having this button lead to the issues page like your initial PR. Seeing as it is a secondary button, consider having it white. This should direct the visitor's eyes after the join intersect button.

[danbaruka]

Hi @IanoNjuguna, can you fix this conflict, so we can merge this PR ?

Thanks

[danbaruka]

LGTM

Code review threshold is met :)