fix(SF2.0/UpcomingDepartures): Handle trips that visit stops multiple times

[joshlarson]

Scope

Asana Ticket: [SF/UD] All Modes: Disambiguate upcoming departures by trip ID AND stop sequence

Implementation

This does two things:

• Adds stop_sequence to the %UpcomingDeparture struct and uses that as well as trip_id to set the HTML element ID for the upcoming departure rows, thus removing duplicate ID's on certain pages. This fixes a bug, because LiveView gets pretty confused when there are duplicate ID's on live-updating elements (see screenshot below).
• Uses stop_sequence as well as stop_id to determine which stop to highlight in the expanded trip details.

Screenshots

Duplicate ID Behavior

Better stop-pin markers

How to test

Visit a route/stop combo that's visited multiple times by the same trip (e.g. the 8 at Ruggles), and expand different departures for the same trip (for the 8 at Ruggles, you'll be able to tell because they come in pairs separated by 1-2 minutes). Rejoice that each trip details only has one stop pin, and the stop pins are different between them (for the 8 at Ruggles, the first one will have a pin at Upper Busway and the second will have a pin at Lower Busway Lane 1).

You could also check the 120 at Orient Heights - there won't be duplicate departure rows, because the second visit is the end of the trip, but you can still rejoice at the absence of a stop pin on the second Orient Heights visit in trip details.