[FR]: PokerGame-Class-Review-Testing

[anshulrastogi9]

Issue: Review and Testing of PokerGame Class
Is your feature request related to a problem? Please describe.
The PokerGame class is the overarching controller for the poker game, and its logic is critical for the smooth functioning of the entire game flow. However, the current implementation has not been thoroughly reviewed or tested, leaving potential bugs, inefficiencies, or missing edge case handling unaddressed. A comprehensive review and testing process is required to ensure the class meets its roles and responsibilities effectively.

Describe the solution you'd like
Conduct a detailed review and testing of the PokerGame class with the following objectives:

Unit Testing:
Write unit tests to cover all methods, including initialization, player management, phase transitions, pot handling, and event emission.
Test edge cases, such as games with the minimum (2) and maximum number of players.
Integration Testing:
Verify integration with dependent classes like PokerPhase, Deck, and PokerPlayer.
Ensure smooth transitions between phases and proper communication between components.
Validation of Responsibilities:
Confirm that the class adheres to its roles:
Game initialization.
Phase management.
Player and pot management.
Community cards handling.
Event emission.
Error Handling:
Validate that proper errors are thrown for invalid configurations, such as starting a game with fewer than two players.
Test how the game handles unexpected situations, like an empty deck or all players folding.