Experimental anti-phasing code change

[Z-Man]

I changed the code that is supposed to prevent phasing incidents by copying walls from the temporary, unsafe, datastructures to the final, safe datastructures.

Watch out for stuff like phasing (obviously), holes in wrong places, invisible walls and other wall-related bugs (mostly "fresh" walls) in the next days and weeks.

I first updated Sumo with the new code, I don't want to expose too many people at once to it Fortress will follow tomorrow.

[Z-Man]

More experimental (social) bugfix code

The bits that try to avoid rubberless deaths of low-ping players is now activated. Again, watch for phasing bugs.

Old clients that switch into spectator mode would delete their player info, taking them out of the target zone of kick votes. Well, now, the player info is kept alive by the server as long as the client stays connected.

Kick votes can only be submitted when you've been online and without name change for five minutes (configurable, of course). Issuing a kick vote freezes your name like being kick-voted already does.

Kick statistics are now persistent over server restarts. So far, only the resulting bans have been stored. That was the last bit of non-persistent infortmation.