feat: Add Movie Collection App with Movies, Actors, and Genres CRUD

[fahrigedik]

Summary

Complete implementation of a Movie Collection application with three core entities, full CRUD operations, and relationship management across all ABP layers.

What's New

Entities & Relationships

• Genre — Name, Description
• Actor — Name, BirthDate, Biography
• Movie — Title, Year, Description, Rating, ImageUrl, GenreId, ActorIds
• Genre → Movie: One-to-many relationship (dropdown selection)
• Movie ↔ Actor: Many-to-many relationship (embedded ActorIds list in MongoDB)

Backend (.NET / ABP)

• Domain entities (AuditedAggregateRoot<Guid>) with validation constants
• MongoDB collections with AddDefaultRepositories()
• Application services with full CRUD, lookup endpoints, and referential integrity checks
• Mapperly-based object mapping (zero-reflection)
• ABP Permission system: 12 permissions (3 entities × 4 CRUD operations)
• Localization keys in en.json for all UI labels, menus, and error messages
• Seed data: 3 genres, 3 actors, 3 movies with TMDB poster URLs

Frontend (Angular)

• Movies page: Responsive card grid layout with poster images, rating badges, genre tags, and actor lists. Hover animations and placeholder for missing images.
• Genres page: Standard table-based CRUD
• Actors page: Standard table-based CRUD with date picker and textarea
• Movie form includes genre dropdown and actor multi-select (checkboxes)
• Manual REST proxy services (models, services, barrel exports)
• Lazy-loaded routes under "Movie Collection" navigation group

Removed

• Book entity and all related code across every layer (Domain, Application, Contracts, MongoDB, Angular, Tests, Permissions, Localization)

Screenshots

Add screenshots after running the application.

How to Test

# 1. Start MongoDB locally
# 2. Seed the database
dotnet run --project src/MovieCollectionApp.DbMigrator

# 3. Start the API host
dotnet run --project src/MovieCollectionApp.HttpApi.Host

# 4. Start Angular
cd angular && npm start