feat: add project metadata validation (#105)

[prasiddhi-105]

Summary

This PR implements robust validation for data/projects.json during the project generation process to ensure every project meets the required schema before deployment.

Changes Made

• Added automated validation checks inside scripts/generate-projects.js:
  • Verified that required metadata fields (title, category, path) exist and are non-empty.
  • Verified that project paths exist on disk.
  • Added duplicate detection to reject duplicate project paths and titles automatically.
  • Configured the script to exit with an error code and display clear error messages if validation fails, preventing broken projects from appearing on the homepage.

Related Issue

Closes #105

Type of Change

• 🐛 Bug fix
• ✨ New feature
• 📝 Documentation update
• 🎨 UI/style change
• ♻️ Refactor (no functional change)
• 🧪 Tests
• ⚙️ CI/tooling

Checklist

• I am a ECSOC26 contributor
• I have read CONTRIBUTING.md
• My branch is up-to-date with main
• I have tested my changes locally
• I have not merged my own PR
• I have verified that licensing and third-party asset attributions are explicitly documented (if applicable)

Packages Added (if any)

N/A

Screenshots / Video (if applicable)

N/A

[vercel]

@prasiddhi-105 is attempting to deploy a commit to the facelessism Team on Vercel.

A member of the Team first needs to authorize it.