MainRun is oneWay trip only -> add option for return leg

[kt86]

In the MainRunCarrierScheduler, the tour is constructed manually.

Currently, it is only a one Way trip from the previous Hub (Depot) to the next one.
This is okay for long distance, but probably wrong for urban contexts.

See also the comment in the code, where the last leg is created (manually)

logistics/src/main/java/lsp/usecase/MainRunCarrierScheduler.java

Lines 137 to 142 in f5073f0

	tourBuilder.addLeg(new Leg());
	tourBuilder.scheduleEnd(Id.create(resource.getEndLinkId(), Link.class));
	//TODO: Option einfügen, dass es auch noch eine Fahrt zurück zum Depot gibt?
	// Würde das optional machen, weil es ja nach Kontext Sinn ergeben kann (urban) aber nicht muss (langstrecke)
	// Bei der Langstrecke kann man annehmen, dass das Fahrzeug ab dem Ziel einen neuen Auftrag nach irgendwo erhalten kann.
	// Urban wird es eher ans Depot zurück kehren.

[kt86]

The implemented approach does not work to 100% as it should.

• switch works
• Vehicle returns to the start location - if this option is set -> link enter/leave events are there :)

BUT:

• Logging of unloading (and handling in the hub) are now too late :(
  Reason: This is executed by an FreightTourEnds event. Unfortunately this is thrown when the vehicle has returned to its origin and not, when leaving after unloading all goods.

Solution tried: Adding another sequence of Start / Leg / End to the tour. But this does not work, because each tour must have exactly one start and one end activity. And this here is violating that rule.

[kt86]

The Events are looking good. Seems, that the logging has a problem -> should be done with removing the shipmentLog #50

(But try to take the idea of logging the "handling" for the missing "handle"-events -> #48 )