[Docs]: Add Comprehensive GitRank Rating Points Formula and Calculation Guide

[indresh404]

Description

• Description:
  Add details to README.md and docs/CONTRIBUTING.md describing how GitRank points are calculated (Commits -> +2, PRs -> +5, Reviews -> +10) and streak scoring rules, so developers understand exactly how they earn XP points on RankerHub.

[github-actions]

Thank you for opening this issue, @indresh404! 🚀

A maintainer (@indresh404) will review this and assign it to you if the issue is valid. Please wait for assignment before you start working on it!

Happy contributing! 🌟

[uNikhil-codes]

Hi @indresh404

To help developers understand exactly how they earn XP points on RankerHub, I propose adding a clean, visually structured section to both README.md and docs/CONTRIBUTING.md.

Here is a preview of the layout and sections I plan to integrate:

---

🎮 GitRank Rating System

GitRank computes a developer's total XP based on active contributions fetched directly from GitHub. Points are calculated using a baseline scoring mechanism combined with daily streak rules.

📊 Core Points Breakdown

Contribution Type	Points Awarded	Description
Commit	+2 XP	For every commit pushed to a tracked branch.
Pull Request (PR)	+5 XP	For every pull request opened or merged.
Code Review	+10 XP	For reviewing and submitting feedback on PRs.

🧮 Calculation Formula

$$\text{Base XP} = (\text{Commits} \times 2) + (\text{PRs} \times 5) + (\text{Reviews} \times 10)$$

🔥 Streak Scoring Rules

To encourage consistent contributions, RankerHub applies daily streak mechanics:

• Streak Maintenance: At least one contribution (Commit, PR, or Review) must be detected daily to maintain the streak.
• Streak Reset: Failing to submit a contribution within the rolling period resets the streak multiplier to 0.
• Streak Bonus: (I will adjust this section to match the exact streak bonus logic implemented in the codebase, such as multiplier percentage or flat XP increments).

---

Please assign this issue to me so I can create the PR and integrate these documentation updates.

THIS IS JUST A PREVIEW OF HOW IT WOULD LOOK
Thank you!

/claim