PR: Implement Request Page Components (Card, Requests, Reject Modal)

[codewkaushik404]

Changes Introduced

• Added:
  • Request page layout and structure.
  • Reusable Card component for displaying request details.
  • Requests component to manage and render multiple request items.
  • Modal component for rejecting requests with proper UI interaction.
• Updated:
  • Integrated request components into the main workflow.
  • Connected modal state handling with request actions.

---

Why This Change?

• Problem: The application lacked a structured interface for viewing and managing incoming requests.
• Solution: Implemented a dedicated Requests page with modular components and a rejection modal to improve request handling.
• Impact:
  • Improves admin workflow by providing a clean UI to review and manage requests.
  • Enhances user experience with structured request cards.
  • Adds rejection functionality through an interactive modal.

---

Screenshots / Video (if applicable)

Before	After
N/A

|

---

Testing

• [] Ran unit tests and all passed (npm test in the relevant directory).
• Manually tested the following scenarios:
  • [x]Test Case 1:** Open Requests page → Requests render correctly.
  • [x]Test Case 2:** Click Reject → Modal opens successfully.
  • [x]Test Case 3:** Confirm rejection → Modal closes and state updates correctly.
• Tested on different browsers (Chrome, Firefox) for UI changes.
• Verified there are no new console warnings or errors.

---

Documentation Updates

• Updated the README.md with new instructions.
• Added clear code comments where logic is complex.
• N/A

---

Checklist

• I have created a new branch for this PR (git checkout -b feature/request-page-components).
• I have starred the repository.
• My code follows the project's coding style and conventions.
• My commit messages are clear and follow the project's guidelines.
• I have performed a self-review of my own code.
• I have added tests that prove my fix is effective or that my feature works.
• All new and existing tests passed locally with my changes.
• This PR introduces no breaking changes (or they are clearly documented).

---

Deployment Notes

• Requires a database migration/schema update.
• Requires new environment variables to be set.
• N/A

---

💬Additional Notes

• Components are designed to be reusable for future request-related features.
• UI structure allows easy integration of approval or additional action workflows in future updates.

Summary by CodeRabbit

• New Features

  • Google + username/password authentication; token and session support.
  • Certificate workflow: create/manage batches, generate/view/download certificates, templates management.
  • Requests system: submit/review/approve/reject with dedicated UI and pages.
  • New dashboard sections: Certificates and Requests pages; batches management UI.

• Improvements

  • Stronger onboarding and login validation; clearer auth responses and redirects.
  • Sidebar, navigation and layout refinements; improved profile photo flows.

• Bug Fixes

  • Safer session/cookie handling and startup error reporting.