Game Logs

Whenever "war" events happen, we want to log them. For now, let's just add the functionality to publish them, and we'll let the messages pile up in the logs queue.

1. Create a function publishGameLog in the src/client/index.ts file that takes a channel, username and a message.
   1. Create a GameLog object (type defined in src/internal/gamelogic/logs.ts) with the following fields:
      1. username: The username of the player who initiated the war.
      2. message: The message describing the war event.
      3. currentTime: The current timestamp as a Date.
   2. Call the publishMsgPack function to publish a message using:
      1. The channel passed in as an argument to publishGameLog.
      2. The topic exchange.
      3. The GameLogSlug.username routing key, where GameLogSlug is a constant in the routing module.
      4. Use the GameLog you created, and send it to the publishMsgPack function.
2. Update the war handler function in the client to publish game logs.
   1. Use the winner and loser properties in the outcome of the handleWar function.
      1. If the outcome is that the opponent won, the message should say "{winner} won a war against {loser}".
      2. If the outcome is that the player won, the message should also say "{winner} won a war against {loser}".
      3. If the outcome is a draw, the message should say "A war between {attacker} and {defender} resulted in a draw".
   2. Publish the logs using the publishGameLog function you created earlier.
   3. If a publishing fails, NackRequeue, otherwise Ack.
3. Test the code.
   1. Spin up two clients and a server. Make sure the game_logs queue exists.
   2. Have one client spawn a unit: spawn americas infantry
   3. Have the other client spawn a unit: spawn europe cavalry
   4. Have the first client declare war by moving a unit into the other client's territory: move europe 1
   5. Repeat with different matchups to trigger each war outcome (you win, opponent wins, draw). You need at least three logs in the game_logs queue before submitting.

You should be able to verify in the RabbitMQ management UI that a log was published to the game_logs queue.

Run and submit the CLI tests.