fix: resolve MongoDB dependency injection errors + add admin features

[RyaninKR]

Summary

• Add party mapping utilities to ClaudeJurySynthesisService for consistent party identification
• Fix fallback synthesis formatting and variable references
• Add admin controller and routes for user management
• Add activity logging system for audit trails
• Fix MongoDB dependency injection errors for Railway deployment
• Resolve "mongoClient.db is not a function" error in admin repositories
• Clean up Python cache files and improve gitignore

Recent Critical Fixes (Latest Commit)

MongoDB Deployment Issues Resolved

• Fixed "No matching bindings found for serviceIdentifier: MongoDBConnection" - Changed all repositories to use TYPES.MongoDBConnection instead of string literals
• Fixed "mongoClient.db is not a function" - Updated admin repositories to accept Db instead of MongoClient
• Removed duplicate MongoDB shutdown callback in index.ts
• Fixed 7 repository files total: User, Contract, OracleDecision, WinnerArgumentsCache, ActivityLog, Post, Comment

Infrastructure Improvements

• Added admin-frontend to gitignore
• Cleaned up Python cache files
• Improved CORS configuration with debug logging

Technical Changes

Core Repository Fixes

• MongoUserRepository.ts: Use TYPES.MongoDBConnection for dependency injection
• MongoContractRepository.ts: Use TYPES.MongoDBConnection for dependency injection
• MongoOracleDecisionRepository.ts: Use TYPES.MongoDBConnection for dependency injection
• MongoWinnerArgumentsCache.ts: Use TYPES.MongoDBConnection for dependency injection
• MongoActivityLogRepository.ts: Use TYPES.MongoDBConnection for dependency injection

Admin Repository Fixes

• MongoPostRepository.ts: Accept Db instead of MongoClient, remove .db() call
• MongoCommentRepository.ts: Accept Db instead of MongoClient, remove .db() call

Container & Index Updates

• container.ts: Use TYPES symbols throughout for consistency
• index.ts: Fix MongoDB connection binding and remove duplicate shutdown callback

Test Plan

• Build succeeds without TypeScript errors
• Application starts successfully with MongoDB disabled (local dev)
• Application properly attempts MongoDB connection when enabled (production)
• No more dependency injection binding errors
• Ready for Railway deployment
• Test party mapping functions with various partyId formats
• Verify admin endpoints work correctly
• Check activity logging is properly recorded
• Ensure AI synthesis still works with the changes

Impact

This PR now includes critical deployment fixes that resolve MongoDB binding errors preventing successful Railway deployment. The application can now start properly in both development and production environments.