Add GameState concept

Closes #46

* Systems are now initialized by their GameState instead of the
  Engine directly
* Mouse and keyboard are not handled by systems anymore, but are
  special objects updated by the Engine object directly
* Saving and loading are not handled by systems anymore, but
  by the Engine object directly
* Entity filters now take the game state instead of the
  entity manager in their init function. The rationale of
  this change is that an entity is better thought of as
  belonging to a game state than to an entity manager,
  which is really just a book keeper.

Fix crash when GameState has no viewport system

Fix ownership transfer of systems when adding new GameState from Lua

Add GameState bindings to Lua

They don't contain anything (yet), but are required because
System::init takes a GameState parameter.

Expose Engine::setCurrentGameState to Lua

Add GameState testing script

Add Lua bindings to all systems

Change MicrobeControlSystem to use Keyboard instead of KeyboardSystem

Fix MicrobeSystem::init() for game states

Switch microbe setup script to game states

Remove deprecated ADD_SYSTEM

GameStates should properly shut down their systems

Remove deprecated files

Re-enable saving / loading

Only allow the Engine to create GameStates

Update documentation

Rename System::active to System::enabled

To avoid confusion with the next commit

Enable systems to react to their GameStates activation / deactivation

This removes the ugly hack of the GameState explicitly asking
the OgreViewportSystem to remove / restore the viewports.

Remove GameState::setPhysicsDebugDrawingEnabled

Clients should just enable / disable the debug draw system

Add GameState::name()

Pass around GameState pointers instead of their names

Add Keyboard::wasKeyPressed and Keyboard::wasKeyReleased

These methods are more convenient than systems keeping track of
the key state themselves. Furthermore, they solve the problem of
systems not knowing the actual key state when activated by
a key stroke.

Make TextOverlaySystem handle state switch gracefully

All overlay elements need to be removed / restored on a state
switch.

Refactor OgreViewportSystem to be closer to TextOverlaySystem

Reduces code duplication

Make Entity class use GameState in its public API

Script authors shouldn't have to care about the EntityManager.
They *should* care about the game state an entity is living in.
This change reflects this.

Unfortunately, since GameState cannot exist without a
full-fledged Engine object, this change makes Entity pretty
awkward to test, so the tests have been removed for now.

Add initializer function to GameState

Update scripts to use GameState initializer

Also adds a SwitchGameStateSystem that toggles between two
alternate microbe universes on pressing F1. Purely for testing.

Reinstated entity test

Only switch game state at the beginning of a frame

Immediately activating a game state during setCurrentGameState
can potentially cause problems as the systems are only partially
updated during the current frame.

Make EntityFilter handle additions / removals in the same frame

If an entity is added to a filter and then removed during the
exact same frame (and before clearChanges() has been called on
the filter), remove that entity from the addedEntities collection
and *don't* add it to removedEntities. For an observer of the
filter, it's as if the entity never existed, after all.

Remove debug output

Safeguard some systems against loading, then switching game state

For RigidBodySystem, OgreCameraSystem and OgreLightSystem, there
is a situation where a new game is started, a savegame is loaded
and then the gamestate is switched. The systems try to remove
internal data structures because due to the game loading, some
entities were removed. Those entities were never initialized with
internal data, however, which can lead to crashes when trying
to remove that data.

The simple solution is to skip the removal for non-initialized
internal data.

Clear entity changes after restoring all entities

TextOverlaySystem and OgreViewportSystem reinitialize all their
entities on activation. Not only is it efficient to clear their
filters' changes after that, it also prevents a crash related to
loading a savegame.

The crash occurs when a savegame is loaded that contains
matching entities with the same id as the current game. In the
systems' activate functions, the newly loaded entities' internal
state is restored. However, the entity filter still has those
ids in its "removed" set as they were also present in the old game
world and have been replaced. Thus, the internal state of the
entities is cleared during update(). Unfortunately, this doesn't
clear the component's pointer to the internal state, which makes
it difficult to detect that situation and deal with it accordingly.

The easiest solution is the one implemented. Resetting the
entity filter will prevent the unwanted clearing of internal
state.

Add missing documentation

Remove unused code

Rename Engine::addGameState to Engine::createGameState

Add Engine::getGameState()

Update documentation

Fix spawn system initialization in game state
Merge pull request #63 from Revolutionary-Games/46_gamestates

GameState