feat(ev): EV contrib compatible with DSim

[Janekdererste]

This PR makes the infrastructure in ev contrib compatible with DSim. It only changes the parts related to the simulation. Statistics are not touched yet and do not work correctly with DSim. This will be fixed in a separate PR.

Mostly it makes the used engines and Handlers aware of partitions. Things that had to be changed:

• ChargerInfrastructure is created per simulation process: Only chargers located on the partition are added to the infrastructure collection
• ElectricFleet interface better schields the underlying vehicle collections and has two implementations:
  1. GlobalElectricFleet creates all EVs at the beginning of an iteration. This variant can be used for a QSim.
  2. DistributedElectricFleet creates EVs lazily when queried for it. It also listenes for vehicles leaving partition and transfer the charging state of the corresponding EV to the next partition. Callers are responsible for only quering EVs that are actually present on the partition. Otherwise the distributed fleet will create duplicate vehicles.
• DistributedDriveDischargeHandler is partition aware and sends drive state to other partitions when vehicles cross partition boundaries. The handler dispatches DischargeEvents immediately instead of delaying them for one second, as there are no race conditions between mobsim and event handling in DSim
• VehicleChargeHandler is now ChargingActivityEngine. This handler queried the mobsim for agents, which is not supported by DSim. Agents are added to this engine if they want to perform a charging activity. This way it is not necessary to query the global agent state of the mobsim. Also, the engine has ownership of agents peforming a charging activity, which is a cleaner desing, since the Engine is modifying the agent plans if they are queuing at a charger
• DistributedWithinDayEvEngine mimics the behavior of the WithinDayEvEngine. Since the distributed simulation cannot give global access to agents the new engine acts as an activity engine. When agents start an activity we can be sure to have a local reference to that agent and that altering an agentś plan is save at that moment. It also is a departure handler for the same reason. Agents can find charging alternatives on departure. The engine always returns falsefor departures, signalling, that another engine should actually handle the agent`s leg.
• DistributedChargingReservationManager provides functionality to reserve chargers across domain boundaries. Agents can request a reservation for a charger and the manager requests the reservation from the on the partition where the charger is located. The new manager uses a callback to inform callees about the result of the reservation request, as the described roundtrip takes at least one simulation time step.

Breaking changes

(dis)charging events are generated one timestep earlier compared to the original QSim code. Event handlers can be called directly from the simulation process so that it is not necessary to mitigate for race conditions between mobsim and event handling. The original code did that by delaying calculations and event dispatch by one second. I think not waiting one second is closer to the expected outcome and justifies a breaking change.

Plug- and Unplug events have different timestamps for the same reason.

Reservations may take +1 time step, as making a reservation might require a messaging roundtrip to another partion. This is also not deterministic at the moment and depends on where chargers are located.