(SR NO - 7) Added FastAPI Backend for GitHub Repository Stats Fetching with Modular Structure and CORS Support

[SharkyBytes]

📝 Description

This PR introduces a FastAPI backend to dynamically fetch GitHub repository statistics using the GitHub API. The implementation allows users to provide a repository URL, and the backend processes the request to return detailed metrics such as contributors, issues, pull requests, and more. Additionally, it includes CORS support for seamless frontend-backend communication.

The following key features were added:
->GitHub repository stats fetching: Extracts contributors, commits, issues, pull requests, community health metrics, and code activity.
->FastAPI integration: Modular backend setup with routing and middleware.
->Environment variable management: Securely manages the GitHub access token using .env.
->CORS middleware configuration: Allows requests from http://localhost:5173 for frontend compatibility.
-> Also updated the README file for setting up the Github Access Token

🔧 Changes Made

->Integrated FastAPI backend with modular structure:
->Added functionality to fetch GitHub repository statistics:

1. Contributors (login, contributions, avatar).
2. Recent commits (author, message, timestamp).
3. Issues (total, open, closed, labels).
4. Pull requests (total, merged, draft).
5. Community health metrics (README presence, license availability).
6. Code activity metrics (weekly commits, additions/deletions).
7. Configured .env file for secure GitHub access token management:

->Configured CORS middleware:

• Allowed cross-origin requests from http://localhost:5173.

📷 Screenshots or Visual Changes (if applicable)

Response On Git Bash

✅ Checklist

• I have read the contributing guidelines.
• I have added tests that prove my fix is effective or that my feature works.
• I have added necessary documentation (if applicable).
• Any dependent changes have been merged and published in downstream modules.

[SharkyBytes]

Hey @chandansgowda, could you please take a look at this as well?

[chandansgowda]

@kartikbhtt7 please review

[smokeyScraper]

@SharkyBytes, please refer to #34 , The embedding service was segregated from VectorDB one (app/core/services) and that's what causing a problem. You might have picked a PR prior to SR 5.

[smokeyScraper]

@chandansgowda, this seems good to go. can be merged...