Moving client and player data into manager classes

Remember: anything with "manager" in its name organizes a number of other
objects, as far as I'm concerned.

I'll eventually have a database connection in the PlayerManager class;
this'll make it easier to manage the database.
Connection and disconnection are working correctly

I've dummied out the player code, so only the client connection code is
working. Otherwise the protocol hasn't changed.

I've also made a few other tweaks as I went along, but nothing really
major.
Added lua, added db connection to PlayerManager

I've also revised the startup process a bit.
Added dummy serialization functions
This isn't fucking working
Serialization is finally functional
Slight code tweak
Merge branch 'serial' into server (read more)

Conflicts:
	server/server_application.cpp (resolved)

After completing the serialization code, I'm merging it into the server's
development branch. This means that although the connection and
disconnection functionality work, I still need to test the player systems
from the new server with the new serialization code.

Immediately following this commit, I'll be merging the minor tweaks to the
editor from the master branch into this one.
Merge branch 'master' into server
Working on reimplementing the player characters

I've also added EraseIf() to the manager classes.
Nothing special, just commiting minor changes
Added a brand new bug, I hate this branch
Another worthless tweak
Fixed the crash bug
Merge branch 'server' (read more)

The only different between this commit and the currently stable branch is the
serialization code and a slight tweak to the server's startup sequence. I tried
to refactor the server, by moving the clientMap and playerMap into their own
wrapper classes, but that failed miserably. I need to stop getting so worked up
all the time, I've wasted way too much time already.