[codex] Add full-stack BookMyVenue MVP

[tuttu5301]

Description

Adds a Phase 1 full-stack BookMyVenue MVP while preserving the existing community documentation and repository setup.

The submission includes:

• a React frontend for authentication, venue discovery, venue details, favorites, and booking flows
• a Django REST Framework backend for users, venues, favorites, and bookings
• database migrations, API tests, frontend tests, and sample venue seeding support
• environment examples and repository ignore rules for local configuration and generated files

The original local work had an independent Git history. This PR branch was rebuilt directly from upstream/main, then the application files were transferred without deleting or rewriting any existing upstream files.

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 19, React Router, Axios
• Backend: Python, Django, Django REST Framework
• Database: SQLite for local development

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

Validation

• Django system check passed
• Django test suite: 7 tests passed
• React test suite: 15 tests passed
• React production build completed successfully

The React build currently reports accessibility warnings for placeholder/empty anchor targets. These are disclosed here for follow-up before the PR is marked ready.

Checklist

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

AI Disclosure

AI tools were used to assist with parts of the implementation and to repair the repository history for this PR. Automated validation has passed as listed above; a final author review is recommended before marking the PR ready for review.

Screenshots / Screen Recording (if applicable)

Not included in this draft.