feat: enhanced waitlist and contact components

[msaeedsaeedi]

Description

This PR introduces contact management and waitlist enhancements across both the backend and frontend.

Changes Included

• Introduced a new Contact table in R1.
• Expanded the Waitlist table schema in R1 with additional fields.
• Added two new backend API routes:
  • GET /waitlist/count
  • POST /contact
• Integrated waitlist and contact APIs into the frontend.
• Implemented a success email mechanism for waitlist submissions.

Motivation

These changes improve lead collection and user engagement by supporting contact form submissions, enhancing waitlist data capture, providing waitlist metrics, and sending confirmation emails after successful waitlist registration.

Related Issues

Fixes N/A

Closes N/A

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update (non-breaking change to README, docs, or guides)
• Refactoring (code reorganization, styling, or performance improvement with no user-facing changes)

How Has This Been Tested?

• Local Build: Ran npm run build and compiled successfully with no errors.
• Lint/Format Check: Ran npm run lint and all Biome rules passed.
• Browser Testing: Tested and verified page rendering and interactions on:
  • Chrome / Firefox / Safari
  • Mobile viewports (if applicable)

Manual Verification

• Verified waitlist submissions are successfully persisted.
• Verified waitlist count endpoint returns the expected count.
• Verified contact form submissions are stored correctly.
• Verified frontend integration with both waitlist and contact APIs.
• Verified successful waitlist submissions trigger confirmation emails.

If applicable, please attach screenshots or screen recordings demonstrating the visual/behavioral changes.

Checklist

• My code follows the style guidelines of this project (run npm run lint:fix and npm run format:write locally).
• I have performed a self-review of my own code.
• I have commented my code, particularly in hard-to-understand areas.
• I have made corresponding changes to the documentation (if applicable).
• My changes generate no new warnings or console errors.
• I have linked any related issues.