MATSim Code

cleanup

in cadyts, the controlerlistener ("context") is now responsible for registering selected plans with the calibrator

fail if adding twice the same strategy to the same subpopulation

Had some unexpected behavior because of that in Zurich, where one of our
scenarios had some strategies defined twice, to have more complex weight
evolution from the config file. This used to work, as the factory was
called each time, and thus a new instance was passed for each setting.

in cadyts, the controlerlistener ("context") is now responsible for registering selected plans with the calibrator

MATSIM-215: Allow getValue() to return <null>: getParams() does in this case also puts the "null" String

Most tests expect this behavior (and the getParams() code goes in this
direction as well)

MATSIM-215: pass remaining config groups to ReflectiveModule

almost all use RefelctiveModule, and all understand null now.

MATSIM-215: playgrounds and contrib ignore "null" in add_param

MATSIM-215: fix more config groups using ReflectiveConfigGroup

MATSIM-215: fix StrategyConfigGroupTest

implied also fixing other default modules, that failed in the IO
process. Fixes are mostly amoving from ConfigGroup to
ReflectiveConfigGroup, allowing to get the automatic handling of null
strings.