fix(SF2.0/UpcomingDepartures): Better readout for early and delayed CR trips

[joshlarson]

Scope

Asana Ticket: [SF/UD] 👂🐞 Crossed out "scheduled at" CR times are read out as regular times

Implementation

• Replaced the {:scheduled_at, time} arrival substatus with {:delayed_from, time} and {:early_from, time}, since even though the visual display is the same for both, the readout is different.
• Applied aria-labels to the substatus components of "Delayed from time" and "Early; Originally scheduled at time".

Screenshots

Delayed

Early

How to test

Find a trip* that's running early or late. Right-click on the HH:MM hh:mm display and inspect accessibility attributes (in Firefox at least - I'm not sure how to do this in Chrome or Safari). OR navigate through the page with a screen reader.

*Finding a trip can be a bit annoying. I usually go either linearly or randomly through the list of CR routes, and for each route/direction combo, I look at the second-to-last stop. If there are any trips with realtime info, then I look to see where they are now, go to that stop, and then look at each stop progressing as the train would until I find a stop that matches what I'm looking for (I start where the train currently is because predictions seem to be more likely to be "on time" when they're further away from where the train actually is).

[thecristen]

Totally on board with the backend change, just want to reuse our time formatting function.

[thecristen]

suggestion: instead of repeating this time formatting over and over, let's re-use <.formatted_time /> (perhaps needs modifying so it can support aria-label)

[joshlarson]

I do support this for consistent time displaying, but the aria label still needs the formatted time (otherwise it reads out the whole datetime, rather than a nice audibly formatted time).