feat: update injection structure

[sebhoerl]

From now on, multipurpose tools such as the scenario cutter or the standalone mode choice scripts will need to be told which EqasimConfiugurator to use. There is the IDFConfigurator, SwitzerlandConfigurator, etc. The reason is that routing and other components may be configured differently depending on the use case, and this should also be reflected when calling those tools.

In principle, there is nothing to be done, because the correct configurator is read from the eqasim.properties file in the resources of the JAR. This means that a JAR built for ile_de_france will define the correct configurator in that file, the same is true for the other currently existing cases. So calling RunScenarioCutter from a switzerland JAR will automatically make use of the SwitzerlandConfigurator.

There are cases where you might want to override the configurator. This can be done (for the time being) by passing the command line option --eqasim-configurator org.eqasim.etc.MyConfigurator, but we will phase out this option in the near future. Alternatively, the configurator can be overridden by defining the environment variable eqasim_configurator before running Java.

Development

• Use Controler.getInjector to set up anything that needs injection (routing, mode choice, simulation, ...) to ensure the same set-up everywhere
• Factor out mode-choice-specific configurator, use the general one instead
• Enforce the use of a EqasimConfigurator that needs to be passed to the respective run scripts
• Define some mechanism that avoids having to pass the configurator name to every script