PlayerOption sometimes sent with only one argument

It seems that sometimes the game sends PlayerOption commands with only a single argument. We should figure out what these commands look like, when they are sent, and what purpose they serve. For now they are simply ignored.

```
ERROR Sep 12 15:46:32 GameConnection Bad command arguments
Traceback (most recent call last):
File "/code/server/gameconnection.py", line 204, in handle_action
await COMMAND_HANDLERS[command](self, *args)
TypeError: handle_player_option() missing 2 required positional arguments: 'command' and 'value'
```