v1.1.1

Bug fix

Service alert sensor now shows active alerts

The alert sensor was always showing 0 even when disruptions existed.

Root cause: the integration was only calling /haltes/storingen
which returns direct stop-level breakdowns (rare). The actual active
alerts (route diversions, construction works) are in /haltes/omleidingen
which was not being fetched.

Fix: both /storingen and /omleidingen are now fetched and merged
for every configured stop. The alert sensor correctly reflects all
active disruptions.

Test stop with active alert

To verify: add stop 207104 (entity: Oost-Vlaanderen) —
it has an active alert: "Werken aan stationsgebouw thv halte".