feat: gamification badges (Issue #1539)

[anshika1179]

What does this PR do?

Solves Issue #1539 by introducing Gamification Badges.

• Updates Prisma schema with Badge and UserBadge models to support many-to-many badge relations.
• Implements gamificationRoutes.js and gamificationService.js to handle awarding and fetching badges.
• Creates BadgesList.jsx to render a user's earned badges in a grid on their profile page with tooltips.

Type of Change

• New feature (non-breaking change which adds functionality)

Tested

• Tested locally (Badges list gracefully handles empty states and renders properly alongside reputation)

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code

[vercel]

@anshika1179 is attempting to deploy a commit to the ayushh-sharmaa's projects Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

⚠️ Merge Conflict Detected

Hey @anshika1179! Your PR #4569 has a merge conflict with main that must be resolved before it can be merged.

🔧 How to fix it locally

# 1. Fetch the latest changes
git fetch origin

# 2. Switch to your branch
git checkout feat-1539-gamification

# 3. Rebase onto the base branch  (recommended)
git rebase origin/main
# — OR — merge it in
# git merge origin/main

# 4. Resolve conflicts in your editor, then:
git add .
git rebase --continue   # (if rebasing)
# git commit            # (if merging)

# 5. Push your branch
git push origin feat-1539-gamification --force-with-lease

💡 Tips

• Use git status to see which files have conflicts
• Look for <<<<<<, ======, >>>>>> markers in conflicted files
• VS Code and IntelliJ have built-in merge conflict UIs

Once you push the fix, this label will be removed automatically. 🚀

NexaSphere automation · Mentor: @Ayushh-Sharmaa

[github-actions]

✅ Merge Conflict Resolved

The merge conflict has been resolved — this PR is now ready for review! 🎉

NexaSphere automation

[github-actions]

⚠️ Merge Conflict Detected

Hey @anshika1179! Your PR #4569 has a merge conflict with main that must be resolved before it can be merged.

🔧 How to fix it locally

# 1. Fetch the latest changes
git fetch origin

# 2. Switch to your branch
git checkout feat-1539-gamification

# 3. Rebase onto the base branch  (recommended)
git rebase origin/main
# — OR — merge it in
# git merge origin/main

# 4. Resolve conflicts in your editor, then:
git add .
git rebase --continue   # (if rebasing)
# git commit            # (if merging)

# 5. Push your branch
git push origin feat-1539-gamification --force-with-lease

💡 Tips

• Use git status to see which files have conflicts
• Look for <<<<<<, ======, >>>>>> markers in conflicted files
• VS Code and IntelliJ have built-in merge conflict UIs

Once you push the fix, this label will be removed automatically. 🚀

NexaSphere automation · Mentor: @Ayushh-Sharmaa