This is now consistent with the other query types.

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

Much more convenient when doing repeated tests.

Besides the basic location/departure/journey queries this also covers
vehicle load information, elevator/escalator status and floating rental
vehicle positions.

Only the request side implemented so far, but enough to show we can get to
everything we need here.

This results in departure information already being shown while the
vehicle layout is still being retrieved.

SBB uses that to mark intermediate stops as POIs (rather than using the
location type for that), e.g. major tunnels. For now we just map that to
the NoService disruption flag as we don't have a POI type yet.

This allows for unified code paths independent of whether vehicle layout
data is already (partially) present, or needs a full query.

This will allow removing the error-prone mode translation code when
importing endpoint configurations eventually.

This affects for example notes for intermediates stops, but also adds
platform and vehicle layout information along the way when available.

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

This will allow providing those information directly from stopover or
journey queries. Most of this is internal for now, the old outward-facing
remains functional. The change to the cache format here is possible as
positive entries have a lifetime in the range of minutes only, so backward
compatibility solves itself quickly.

fixes compile

With the new data sources for this, we are no longer limited to vehicle
layout data for departures, but can also get them for arrivals.

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

We yet have to make use of the results though, which first will require
a few extensions to the JourneySection and Stopover types though.

This now includes support for common.tcpdL and common.stc*L responses,
as well as support for multiple train groups in I.JF remark messages.

There's still more common.tc* fields and I.X* remarks that seem related
but where I have no idea about their content so far. At least neither of
them seems contain the per-coach load information that SBB seems to have
in this context.

Those are found in certain remark messages of SBB journey responses.

This has yet to be integrated, which isn't entirely straightforward as
this doesn't fit the way vehicle layout queries work for the other
backends.

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

Now that we have two sources for this, we can actually get multiple
overlapping results.

ÖBB doesn't provide that detail for example.

Those occur for international stations with non-ÖBB trains.

Those need to be in relative platform coordinates, not meters.