MATSim Code

organize a bit the strategies

difficult to really put them in feature-dependent packages, as most
strategies are multi-feature (basically considering at least
co-travelers' synchronisation and vehicle ressources)

move more usecase-specific classes in the relevant packages

move "joint activities" related classes in an own package

move lots of joint trip related code in an own package

move PlanRouterAlgorithmFactory to socnetsim

only used there

move ScenarioElementProvider to framework

reduce dependencies of framework to rest of the package further

move activation of joint qsim in joint trip module, not base module

first step towards separating "framework" from "use cases"

Removed unused dependencies from the pom.
Added rental parking time fee for free-floating and one-way cs.