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

Bug fixes on 0.5.2-beta

Missing const.py data
Incorrect empty timezone handling

Bug fixes: TZ handling & blocking call

Changes : bug fixes

• Timezone was taken from the datasource agency which for multi-tz countries is not correct. Now it takes the timezone from the stop or, if not available, HA instance, resolves: #107
• When configuring a new entry, a blocking call error was thrown, this has been resolved, resolves: #98

Improve UX on stop selecting

Changes

When selecting start/end stops that did not present a valid route, one had to restart all steps.
Now you return to the screen to be able to re-select stops, addresses: #105

Reduced logging messages