Feat/jabir project structure and backend service

[ja6ir]

Description

This PR delivers a complete Phase 1 MVP of BookMyVenue — a location-based venue discovery and booking platform covering three personas: User, Owner, and Admin. It includes a working FastAPI backend (modular domain structure, JWT + Google OAuth auth, Alembic migrations, seed data) and a React + Vite + TypeScript frontend with role-based flows.

Key capabilities:

• Auth: email/password signup & login (JWT), Google OAuth.
• User: search & filter venues, view details, request bookings, view booking history, cancel (mock refund).
• Owner: submit a venue (status pending), manage listings, accept/decline incoming bookings.
• Admin: approve/reject submitted venues, platform overview stats.
• Payments: mocked (payments record on confirmation, mock_refunded on cancellation).
• Monorepo layout (frontend/, backend/, docs/, docker-compose.yml) with Docker support and smoke tests.
• README merged with the upstream community content + MVP implementation docs.

The work is split into logical commits (scaffolding, backend core, modules, migrations, tests, frontend shell/components, README).

Phase Category

• Phase 1: MVP Submission (Base Foundation)
• Phase 2/3: Feature Implementation or Modularization
• Phase 4: Scalability Optimization
• General (Documentation, Bugfix, Chore, etc.)

Tech Stack (For Phase 1 MVP Submissions)

• Frontend: React 18, Vite, TypeScript, React Router, TanStack Query, Zustand, Tailwind CSS
• Backend: Python, FastAPI, SQLAlchemy 2.0, Alembic, Pydantic v2, JWT auth, Google OAuth
• Database: SQLite (MVP, Postgres-ready via Alembic)

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature / Module (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update

Checklist:

• I have read the Contribution Guidelines.
• My code follows the community spirit and standards of the WeCode community.
• I have performed a self-review of my own code.
• I have commented my code, particularly in hard-to-understand areas.
• My changes generate no new warnings or errors.

AI Disclosure

• I did NOT use AI tools to generate this code.
• I used AI tools (e.g., Copilot, ChatGPT, Claude) to help write this code, and I have fully reviewed, tested, and understand the output.