Moving transit model into a separate module

[leonardehrenfried]

Before we can move transit model into its own module, we need to resolve the following issues:

Bad

• Timetable depends on GTFS-RT
• Transit group priority depends on the RAPTOR API
• TripPattern depends on RoutingTripPattern which depends on the RAPTOR API
• FrequencyEntry depends on Frequency which is a copy from OBA

Undecided

• Lots of model classes depend on framework code: text, i18n, geometry...

Acceptable

• transit model depends on JTS
• transit model depends on org.geojson for which there is no ready-made lib
• transit model depends on the dagger runtime