Added logging to coordinator to identify own bot
Simulate the tank id bug that affected many of us

The commented code simulates a bug that knocked me out the competition.

Many of us had assumed tank id's of 0 to 3, since that's what the
official test harness is programmed to do.

However during the tournament quite a few competitors had bots that
froze because occasionally a different tank id would be used. I had
fallback logic in ScenarioDrivenBot which would run older, simpler bot
logic when an exception occurred. During the knockout round the tank Id
bug must have occurred, because my tanks didn't dodge bullets like they
did in testing.