Optionally query stop sequence during departures request

[alexander-albers]

Some providers allow querying the full journey stop sequence of a line already during the stop departures request. Instead of needing to use subsequent queryJourneyDetail requests, the data could already be returned in the QueryDeparturesResult. The main advantage would be that Efa does not return realtime data for the queryJourneyDetail request, but only during the stop departures request. Disadvantage is greater data usage, which is why this should be made optional.

EFA parameter: includeCompleteStopSeq=1