filter out fields that shouldn't be seen for KILL_PLAYER event, finer grain logic for communicating state for the event

[AlecM33]

• the KILL_PLAYER and ASSIGN_DEDICATED_MOD events were neglecting to invoke the GameStateCurator module to make sure game state is appropriately mapped per the user's permissions. This was causing us to erroneously include a persons cookie and socket ID, which are meant to be seen by the server only and could theoretically be used to assume the role and permissions of someone else during the game.

Fix

Fixes #223

• Edit the events to use the game state curator to properly filter out certain fields.
• Edit the "communicate" function for these events to make sure they are invoking different mapping logic for dedicated moderators vs. everyone else. In particular, if a player is killed and not revealed, moderators should still receive alignment information in the response, while everyone else should not. So if a given server instance has the moderator socket connected to it, communicate a different response to them vs. everyone else.

Testing

• unit tests to verify key components of the fix
• verified that the socket event no longer includes the cookie or socket ID for KILL_PLAYER and ASSIGN_DEDICATED_MOD:

Kill player

also verified the game state looks correct from all the different views (moderator, the player that was killed, and a spectator):

Assign Dedicated Mod -> Kill Player (When a temporary moderator kills the first player, as part of assigning a dedicated mod we also emit the kill player event)