API: New terminus`Stopover` in `trains/trips` is wrongly marked as cancelled

[marhei]

When a train has a new terminus, this stopover is also incorrectly marked as cancelled: true, because in HAFAS the departure (but not the arrival) was marked as cancelled.

Expected behaviour: The parameter cancelled should only be true if both arrival and departure have been cancelled.

Example train today: ICE 316 with new final stop Aachen Hbf, which is returned as cancelled according to API.

[HerrLevin]

Little bit late to the party, but this is what we're getting from the HAFAS API. I'll look into it, wether we can make the cancellation consistent and a bit more... logical.