Add support for NeTex DatedServiceJourneys

[JonathanBrynhagen]

Summary

Created a new object TripOnServiceDate to represent a DatedServiceJourney and adds these to the graph index by creating two new maps.
One is indexed using datedServiceJourneyId and the other using a tuple of tripId and serviceDate. Both return a single TripOnServiceDate.
TripOnServiceDates are also indexed in TimetableSnapshots for when there are realtime updates.

A new GraphQL endpoint is added called datedServiceJourney with which you can retrieve a datedServiceJourney from the graph index (or TimetableSnapshot if there are realtime updates) using a datedServiceJourneyId.
Additionally a field is added to the LegType where you can now retrieve the datedServiceJourney used in that leg aswell following the same logic as above.

Unit tests

A new unit test was added asserting that TripOnServiceDate objects are correctly created during NeTEx mapping.

Code style

Followed the code style included in the repo

Related issue #3150

[t2gran]

We should probably test this, with a dataset with DSJ.

See above

[JonathanBrynhagen]

I get the following error when building with the Norwegian dataset at https://storage.googleapis.com/marduk-dev/outbound/netex/rb_norway-aggregated-netex.zip

"An uncaught error occurred inside OTP: java.lang.NullPointerException: DatedServiceJourney operating-day not found. DSJ Id: GAN:DatedServiceJourney:3964_LE-BDN_21-11-09
java.lang.RuntimeException: java.lang.NullPointerException: DatedServiceJourney operating-day not found. DSJ Id: GAN:DatedServiceJourney:3964_LE-BDN_21-11-09
	at org.opentripplanner.netex.NetexModule.buildGraph(NetexModule.java:117)
	at org.opentripplanner.graph_builder.GraphBuilder.run(GraphBuilder.java:81)
	at org.opentripplanner.standalone.OTPMain.startOTPServer(OTPMain.java:136)
	at org.opentripplanner.standalone.OTPMain.main(OTPMain.java:52)
Caused by: java.lang.NullPointerException: DatedServiceJourney operating-day not found. DSJ Id: GAN:DatedServiceJourney:3964_LE-BDN_21-11-09
	at org.opentripplanner.netex.mapping.calendar.DatedServiceJourneyMapper.mapToServiceDates(DatedServiceJourneyMapper.java:58)
	at org.opentripplanner.netex.mapping.TripCalendarBuilder.addDatedServiceJourneys(TripCalendarBuilder.java:87)
	at org.opentripplanner.netex.mapping.NetexMapper.mapDatedServiceJourneys(NetexMapper.java:362)
	at org.opentripplanner.netex.mapping.NetexMapper.mapNetexToOtp(NetexMapper.java:185)
	at org.opentripplanner.netex.NetexBundle.loadFilesThenMapToOtpTransitModel(NetexBundle.java:165)
	at org.opentripplanner.netex.NetexBundle.lambda$loadFileEntries$1(NetexBundle.java:117)
	at org.opentripplanner.netex.NetexBundle.scopeInputData(NetexBundle.java:141)
	at org.opentripplanner.netex.NetexBundle.loadFileEntries(NetexBundle.java:115)
	at org.opentripplanner.netex.NetexBundle.loadBundle(NetexBundle.java:93)
	at org.opentripplanner.netex.NetexModule.buildGraph(NetexModule.java:78)
	... 3 common frames omitted

The data looks valid to me

I tried reproducing this after @t2gran's PR and that seems to have fixed the issue. If it's still a problem let me know.

[t2gran]

I tried reproducing this after @t2gran's PR and that seems to have fixed the issue. If it's still a problem let me know.

I did fix it, an operating-day (any entity) must be in the same file (group file) or one of its parents, shared group file or shared file.

[t2gran]

@JonathanBrynhagen For next time, I would prefer if you did not "force push" after we have gone fare into the review process😀. I makes it harder to review.