TargetController

@michael-seitz @BZoennchen @dietrich @Isabella-vonSivers 

Es wird Zeit, dass wir das mit der Target Liste angehen.

Ich hab seit gestern Fehler gesucht, weil ich nicht mehr wusste, dass die Modelle selbst die Benutzung der Target Liste der Agents aktivieren müssen (indem der `nextTargetListIndex` auf 0 statt -1 gesetzt wird). Wir sollten das aber zum Standard machen, bevor noch mehr Modelle auf dem deprecated System entwickelt werden und noch mehr Leute Fehler suchen!

Also an alle, die Modelle (insbesondere Modelle mit mehreren Zielen) haben: Bitte mal kurz auf diesem Branch testen.

See merge request !10

Implemented the PedestrianStateProcessor

PedestrianStateProcessor adds a column "state" to the output with the
state of a pedestrian.

The possible states are:
 - c = Pedestrian was created
 - m = Pedestrian has moved
 - d = Pedestrian was deleted (has reached its final target)
 
The state is needed for the UQ simulations.

See merge request !14

PedestrianStateProcessor adds a column "state" to the output with the
state of a pedestrian.

The possible states are:
 - c = Pedestrian was created
 - m = Pedestrian has moved
 - d = Pedestrian was deleted (has reached its final target)
 
The state is needed for the UQ simulations.

If timestamp option in json is set to false, no timestamp is written in the output's folder name.

This floor field processor is independent of the discretization method and has a different output structure than the (old) floor field (grid) processor.

Values are not added always, they are also changed.

If there is a targetId, there must be a target. Otherwise

- someone have removed the target dynamically and forgot to remove the
  targot from the pedestrian's target list (which is a bug)

- or there is another bug that must be fixed

There was a
assert targetIds.size() > 0

That means, this case is not expected, right?
Why is this case handled then in the next lines?

I switched the assert statement against getNextTargetId() which throws
an exception if there is no next target.

Use hasNextTarget() if you have to check this.

It testet for a normal resource file, but unit tests have a different
resource folder. So this cannot be testet.