Scrimmages with teams with faulty submissions go haywire

[n8kim1]

(not fully verified)

when the scrimmage server can't find the bot files properly (eg if the structure of submission is wrong, or if they submit something that's not a bh bot), the scrimmages are marked as errors, and messages stay on the pub/sub

Probably best to ack them, and to introduce a new error state in the database that represents this sort of error? Or, whoever's code is faulty should take an L? (Should still note something like "loss via faulty submission"

Also, how could teams safeguard against this accidentally happening to them? (that they submit something faulty, and take L's) The compile server used to be a safeguard, but we don't have that anymore...