Nicer vehicle location display, bug-fixes

Enhancement: vehicle location display

For the vehicle location entities (geo_location.*), the entity_name has been extended with the transport-type, based on route_type.
This allows to customize the display of the picture in the map-card. For details, see https://github.com/vingerha/gtfs2/wiki/5.-Visualizing-the-data#vehicle-positions.

Possible (!?) breaking change

Due to the enhancement which extends the entity-name of the geo_location entity, you may need to setup your card(s) differently.

Change(s)/Fixes

Fix: real-time trip-updates can be provided only via stop_sequence, which were not taken into account, this fixes: #119
Fix: when a trip is found both in calendar and calendar_dates there was a risk to have duplicate entries, this fixes #118
Fix: incorrect real-time data across TimeZones

Fix issue when RT data only supplies stop_sequence (not stop_id)

Changes

Adding option to retrieve RT trip updates also via stop_sequence
Fixes: #119

Fix issue with duplicate departures due to calendar/dates overlap

Changes

When departure is found both in calendar and calendar_dates there is a risk to have duplicates. By verifying existing entries in the timetable before adding, this is avoided. Added a few debug lines for further support. This addresses #118

Fix RT header, impove error handling for RT request

DEV RELEASE, still in testing

Fix issues with RT data across TZ

DEV RELEASE, still in testing

Local stop: align attributes around realtime data

Changes

Local stop enhancement: time entries for scheduled, realtime and delays were not always conclusive nor aligned on format. This has now been improved by a.o. adding UTC, calculating delays based on time, etc.
This allows users to be more flexible in cards and a.o. show the times in their own format (12h/24h)
See : https://github.com/vingerha/gtfs2/wiki/2c.-Acquire-local-stops-&-departures#local-stop-details-explained

Local stop attributes: show departure realtime as HH:MM

Changes

The format of hte realtime-departure time (in datetime) was inconsistent with the scheduled departure time (in HH:MM), now they are both shown as HH:MM which makes it easier to show in cards (avoiding complex nested attribute handling, resolves #112

Fixes on Timezone, Blocking call a.o.

Changes

• When a data source spans multiple timezones, the times were incorrectly represented, resolves #107
• When configuring a new entry, a blocking call error was thrown, this has been resolved, resolves: #98
• When trying to delete a data source, an error was thrown and nothing deleted, resolves (part of) #110

Possible breaking changes

Due to the high(er) complexity of working with timezones, it may (!) falter on realtime, testing was performed but please report issues ... if any

Fix fixes on TZ

This is a DEVELOPMENT release

Changes

Applying TZ fixes for local-stop, this includes an option to apply a correction to the TZ of the source-file

Breaking changes

Unclear, testing is challenging due to many impacting elements.

Fix timezone: use agency tz

Agency TZ seems to be the leading one, above those of the stops
Logic applied: if Agency TZ then use Agency TZ else Stop TZ else HA/server TZ