feat: implement initial CI pipeline with GitHub Actions (#51) (Apertre3.0)

[Aditya-18849]

I have implemented the automated CI/CD pipeline using Github Actions .... These are the following features that i have implemented :

-----Automated Verification -----:
The .github/workflows/ci.yml file now automatically triggers a virtual ubuntu server whenever someone opens a Pull request to main.

----Multi-Environment Build --------
The pipeline cleanly navigates the monorepo to install dependencies for the root, the React/vite Frontend and the node.js backend separately....

----Security and Stablilty -----
It automatically runs your new linting scripts , builds the frontend to ensure it does not crash , runs an npm audit to check for security vulnerablities

[akshay0611]

Great job getting the GitHub Actions infrastructure in place. Setting up a CI pipeline is a significant contribution toward the long-term stability and reliability of RIVETO.

What makes this a great contribution:

• Monorepo Support: Correctly handling dependency installation for both frontend and backend shows a strong understanding of the project structure.
• Vite Build Verification: Automatically validating the frontend build is a critical safeguard against broken releases.
• Clean Implementation: The workflow is well-structured and aligns with GitHub Actions best practices.

This implementation establishes a solid CI foundation that we can confidently extend with testing, linting, security scans, and deployment stages going forward. Architecturally, this is a meaningful step forward for the community.

Verdict

🚀 LGTM - Merging this.