comm_command

[adrienntindall]

Builds on #1161

This PR is long but ultimately has 3 goals:

1. Fully document the contents of comm_command.c. This file should be reviewed thoroughly, and is thankfully short.

2. Give general names and corresponding constants to each other comm_command_ file, named as such when they contain a CommCmdTable list of functions. These are not intended to be documented further and only the tables themselves need to be looked at when reviewing, since they will contain all already documented functions that had their names changed.

3. Use the COMM_CMD_ constants in appropriate locations in order to maintain functionality when adding new communication functions to the base table. I'm pretty sure I found all instances, but if I missed any I would like that to mentioned as a part of this review.

[scbroede]

imo just like with script commands, these should all be named in the imperative sense (ie. verb-first, phrased as a command). aside from the ones i've individually flagged, commands not already following this convention should have Recv in front.

also this has conflicts

[adrienntindall]

imo just like with script commands, these should all be named in the imperative sense (ie. verb-first, phrased as a command). aside from the ones i've individually flagged, commands not already following this convention should have Recv in front.

also this has conflicts

I think that adding Recv to almost every comm command is gonna be too much, since as stated before they're implicitly receive functions already and that can get really cluttered really quickly.