feat: implement redis caching actor

[haongo138]

Overview

This pull request aims to integrate Redis into our application as an actor, enabling us to cache game state data for future use.

Changes

Implement a StoreActor to handle Redis GET / SET actions:

• Persisting data:
  • Room's scoreboard (game.state.scoreboard) at game end by key room:{room_id}:scoreboard
  • Player info (api_key, team_name) on PlayerJoined message
• An endpoint /rooms/{room_token}/scoreboard to get a finished room's scoreboard
  Example response:

  "scoreboard": [
    {
      "player_id": 0,
      "total_points": 4,
      "api_key": "player_1",
      "team_name": "player_1"
    },
    {
      "player_id": 1,
      "total_points": 1,
      "api_key": "player_0",
      "team_name": "player_0"
    }
  ]
}

[hieuphq]

Can we expose more data? how about name, sth like that. We can't show the data just the id

[haongo138]

Thanks, I just pushed my refactor to include more info (api_key, team_name) in scoreboard response.