Game State Channel Game Start

[BrennanAyers]

Pull Request Template

Description

This PR brings in the functionality for the Game State Channel websocket to begin a Game when enough Players subscribe, and then relay this Game State to all subscribed Players. To facilitate a quick refactor, the number of Players in a Game has been bumped from 2 to 4, and one of the join_game endpoints has been skipped.
The output of the game-started message is exactly the same as the game_state endpoint output, allowing the Frontend to render React accordingly from the Waiting screen to the Game Board screen. It also will not require major refactoring of the processing of tableDeck and other information.
The Game State Channel now will use the private begin_game? method every time a Player subscribes to check if the Game has enough Players. If not, it will move on, otherwise, it will game.start and then send the game-started message containing the full Game State.
For some undetermined reason, the action-cable-testing gem does not play well with FactoryBot, so our create_cards method in the GameStateChannel spec is handling that functionality currently.

Resolves #107

Type of change

Please delete options that are not relevant.

• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• GameStateChannel game-started broadcast spec
• Removal of rejects connections if more than max players join join_game endpoint spec

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes