Implement Game Creation for Moderators with Input Validation and Database Integration#1

### Overview This user story will focus on enabling a moderator to create a new game in the application, facilitating the initiation of game rounds and inviting estimators. The story encompasses creating the necessary UI elements for game creation, input validation, and storing game details in the database. ### User Story **As a** moderator **I want** to create a new game **So that** I can start inviting estimators **Technical** Notes - Create a UI form with fields for game name and description (optional). - Validate inputs to ensure the game name is provided before allowing submission. - Store the game details in a database table `Games` with columns `GameID`, `Name`, and `Description`. Database Table Games: ```sql CREATE TABLE Games ( GameID INT PRIMARY KEY AUTO_INCREMENT, Name VARCHAR(255) NOT NULL, Description TEXT ); ``` - Upon successful creation, generate a unique game ID and allow the moderator to invite estimators via email or in-app notifications. ### Acceptance Criteria - AC1: Game Creation with a Required Name and an Optional Description - **Given** a moderator is on the 'Create New Game' page - **When** they input a game name and optionally a description, and press the 'Create' button - **Then** the game is created in the database with the provided details - **And** a unique game ID is generated - AC2: Input Validation for Game Name - **Given** a moderator attempts to create a game without entering a game name - **When** they press the 'Create' button - **Then** an error message is displayed indicating that the game name is required - AC3: Confirmation of Game Creation - **Given** a moderator has successfully created a game - **When** the game is saved in the database - **Then** a confirmation message is displayed along with the game ID - **And** the moderator is prompted to invite estimators ### Definition of Done (DoD) 1. **DoD1**: Documentation Updated: All technical documentation has been updated to reflect the changes made during the implementation, including any new configurations or dependencies. 2. **DoD2**: Unit tests are written and passing, ensuring the UI form validation and database insertion logic works as intended. 3. **DoD3**: UI components are styled according to the design specifications. 4. **DoD4**: Integration tests confirm that the game creation function interacts correctly with the database. 5. **DoD5**: End-to-end testing confirmed that the user can successfully create a game and receive a confirmation. 6. **DoD6**: The feature has been reviewed and approved by peer code review. 7. **DoD7**: Deployment to the staging environment has been verified with no critical issues.